(Republishing, or using this info in a commercial product/website, is prohibited without permission. All other uses are permitted. If in doubt, please ask.)
This latch class is when a thread is waiting for access to the per-allocation unit extent cache, a cache of extents in the allocation unit where there is at least one page available for allocation. It is more efficient to have a small, in-memory cache of such extents, rather than having to search through the relevant IAM and PFS pages to find unallocated pages. See here and here for more information on IAM and PFS pages, respectively.
(Books Online description: none)
Questions/comments on this latch class? Click here to send Paul an email, especially if you have any information to add to this topic.
Added in SQL Server version:
Removed in SQL Server version:
Extended Events latch_class value:
Maps to the SPACEMGR_AEC map_value in sys.dm_xe_map_values.
The map_key value in sys.dm_xe_map_values is 83 in 2012 and 2014 RTM. After 2014 RTM, you must check the DMV to get the latest value as some map_key values have changed in later builds.
I have not seen this latch be a noticeable contention point.
See the LATCH_EX wait type for more information about latches in general and how to troubleshoot them.
Known occurrences in SQL Server (list number matches call stack list):
- Adding an extent to the extent cache (in this case, while deallocating unused pages from the final extent in a bulk allocation, which preallocates all pages in each allocated extent for efficiency and then cleans up any unused ones at the end)
And many more similar call stacks.
Abbreviated call stacks (list number matches known occurrences list):