使用 Microsoft 登入
登入或建立帳戶。
您好:
選取其他帳戶。
您有多個帳戶
選擇您要用來登入的帳戶。
英文
很抱歉,此文章目前沒有您所使用語言的版本。

Symptoms

In Microsoft SQL Server 2016 and 2017, the temporary table cachestore memory object contention causes the CMEMTHREAD waits, which lead to slow performance.

Cause

A major point of contention in highly concurrent Tempdb workloads which create temp tables in stored procs is the contention on the Temp Table cachestore memory object. This primarily surfaces as CMEMTHREAD waits due to contention on the cachestore memory object when many concurrent workers try to CREATE/DROP the temp tables. Because the cachestore's memory object is not partitioned currently, memory object contention occurs on all the threads.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Resolution

This issue is fixed in the following cumulative updates for SQL Server:

Note: The resolution for the fix is partitioning the memory object (by CPU) that will improve the performance.


About cumulative updates for SQL Server:

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

References

Learn about the terminology that Microsoft uses to describe software updates.

需要更多協助嗎?

想要其他選項嗎?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

這項資訊有幫助嗎?

以下何者是您會在意的事項?
按下 [提交] 後,您的意見反應將用來改善 Microsoft 產品與服務。 您的 IT 管理員將能夠收集這些資料。 隱私權聲明。

感謝您的意見反應!

×