This wait type accumulates while SQL Server is waiting for thread-safe memory object. The most common memory object effected is the plan cache, especially when plans are rapidly added or removed from the cache. This wait is common and moderate values do not indicate major issue. If values are excessive investigation is required

Resolved by


Suggested solutions

    1. Consider enabling Optimize for Ad Hoc Workloads
    2. The links below give details onto how to diagnose other problems from this wait
    3. Ensure any 2008R2 instances have at least CU6 applied

Additional research

How It Works: CMemThread and Debugging Them
SQL Server 2008 R2 performs poorly when most threads wait for the CMEMTHREAD wait type
Diagnosing Plan Cache Related Performance Problems and Suggested Solutions

⇐ Back to index