(Republishing, or using this info in a commercial product/website, is prohibited without permission. All other uses are permitted. If in doubt, please ask.)
Description:
Finally! As of SQL Server 2025, spinlock contention can now be easily tracked and diagnosed using a wait, instead of with Extended Events and callstack analysis. TF 8134 must be enabled (at startup or with DBCC TRACEON).
(Books Online description: “Occurs when a thread is waiting to acquire a spinlock. Includes both the spinning and the sleeping time. High values might indicate spinlock contention. Because of a possibility of a minor performance impact with high throughput and high concurrency workloads, the SPINLOCK_EXT waits are tracked only if trace flag 8134 is enabled.”)
Questions/comments on this wait type? Click here to send Paul an email, especially if you have any information to add to this topic.
Added in SQL Server version:
2025
Removed in SQL Server version:
N/A
Extended Events wait_type value:
The map_key value in sys.dm_xe_map_values is 184 in 2025 RTM. After 2025 RTM, you must check the DMV to get the latest value as some map_key values have changed in later builds.
Other information:
N/A
Known occurrences in SQL Server (list number matches call stack list):
Abbreviated call stacks (list number matches known occurrences list):
