(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 wait type went into disuse before SQL Server 2014, when it was re-purposed as the wait type that occurs when a page is being read from a buffer pool extension file.
(Books Online description: “Identified for informational purposes only. Not supported. Future compatibility is not guaranteed.”)
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:
Removed in SQL Server version:
Extended Events wait_type value:
The map_key value in sys.dm_xe_map_values is 182 in 2008 and 2008 R2, and 186 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.
If this wait type is prevalent, that indicates that a large number of buffer pool extension reads are occurring. This may or may not be a performance issue, depending on the type of queries that are leading to BPE reads, as a BPE read is one page at a time. Single-threaded (or low degree of parallelism) scans will be most affected by having data in the BPE, and performance of these queries can be improved by using a higher degree of parallelism or removing the BPE.
Known occurrences in SQL Server (list number matches call stack list):
- Waiting for a page to be read from the buffer pool extension (in this case, while reading rows from a table)
And other similar call stacks.
Abbreviated call stacks (list number matches known occurrences list):