SQL Server等待事件—PAGEIOLATCH_EX

時間 2020-02-15

標籤 sql server 等待事件 pageiolatch 欄目 SQL 简体版

原文原文鏈接

什麼是PAGEIOLATCH_EX等待事件？下面咱們將對PAGEIOLATCH_EX等待事件的相關資料作一個簡單的概括、整理。關於PAGEIOLATCH_EX，官方文檔的簡單介紹以下：sql

PAGEIOLATCH_EX：數據庫

Occurs when a task is waiting on a latch for a buffer that is in an I/O request. The latch request is in Exclusive mode. Long waits may indicate problems with the disk subsystem.緩存

在任務等待 I/O 請求中緩衝區的閂鎖時發生。閂鎖請求處於「獨佔」模式。長時間的等待可能指示磁盤子系統出現問題。ide

In SQL Server, a latch is a short-term lightweight synchronization object.ui

Buffer latches including the PAGEIOLATCH_EX wait type are used to synchronize access to BUF structures and associated pages in the SQL Server database. The most frequently occurring buffer latching situation is when serialization is required on a buffer page. These buffer latches are not held for the complete period of the transaction. The PAGEIO latches are a subset of BUF latches used when the buffer and associated data page or the index page is in the middle of an IO operation. PAGEIOLATCH wait types are used for disk-to-memory transfers.this

在SQL Server中，閂鎖是短暫的輕量級同步對象。spa

緩衝區閂鎖（包括PAGEIOLATCH_EX等待類型用於同步訪問SQL Server 數據庫中的 BUF 結構和關聯頁。最多見的緩衝區閂鎖狀況是在緩衝區頁面上須要序列化操做時。這些緩衝區閂鎖不會在事務的整個期間內保持不變。PAGEIO閂鎖是緩衝區和相關數據頁或索引頁處於 IO 操做中間時使用的 BUF閂鎖的子集。PAGEIOLATCH 等待類型用於磁盤到內存的傳輸。線程

PAGEIOLATCH_EX (exclusive mode page IO latch request)orm

When a SQL Server user needs a page that is not in buffer cache, the database must first allocate a buffer page, and then puts an exclusive PAGEIOLATCH_EX latch on the buffer while the page is transferred from disk to cache. During this operation SQL Server puts a PAGEIOLATCH_EX request on the buffer on behalf of the user. After the write to cache is complete, the PAGEIOLATCH_EX latch is released.server

當SQL Server用戶須要不在緩衝區高速緩存中的相關頁面時，數據庫必須首先分配一個緩衝區頁面，而後在頁面從磁盤傳輸到高速緩存時，在緩衝區上放置一個獨佔PAGEIOLATCH_EX閂鎖。在此操做過程當中，SQL Server 表明用戶在緩衝區上發出PAGEIOLATCH_EX請求。寫入高速緩存完成後，將釋放PAGEIOLATCH_EX閂鎖。

Problem indication

Excessive PAGEIOLATCH_EX waits occur when data is transfered from disk to memory for update operations and these transfers take time to complete.

This may be an indication of disk contention or other disk subsystem bottlenecks.

當數據從磁盤傳輸到內存中以進行更新操做時，將出現大量的PAGEIOLATCH_EX等待，而且這些傳輸（磁盤IO操做）須要時間才能完成。這可能代表存在磁盤爭用或其餘磁盤子系統瓶頸。

PS：其實當一個大表發生大量數據刪除操做時，也會出現大量的PAGEIOLATCH_EX等待事件。

Description:

This wait type is when a thread is waiting for the read of a data file page from disk to complete, and the thread is going to modify the page structure once it is in memory (EX = EXclusive mode). The Latches Whitepaper in the sidebar on the right has a description of all latch modes and their compatibility with other latch modes.

(Books Online description: 「Occurs when a task is waiting on a latch for a buffer that is in an I/O request. The latch request is in Exclusive mode. Long waits may indicate problems with the disk subsystem.」)

這種等待類型是線程正在等待從磁盤讀取數據文件的相關頁面到內存的完成，而且一旦線程將修改內存中的頁面結構（EX = EXclusive模式）。右側邊欄中的「閂鎖白皮書」介紹了全部閂鎖模式及其與其餘閂鎖模式的兼容性。

（在線叢書描述：「當任務正在等待I / O請求中的緩衝區的閂鎖上時發生。閂鎖請求處於互斥模式。長時間等待可能代表磁盤子系統有問題。」）

PAGEIOLATCH_EX

A query is waiting for exclusive write access to a page in order to add data to the page, but the page is not currently in memory and has to be loaded from disk.

Page latches are lightweight, non-configurable locks used by internal processes within SQL Server to manage access to the page buffer in memory. When SQL Server has to read pages from the disk into the memory buffer or from the buffer out to disk, it must place latches on the buffer pages while the processes take place.

It’s normal to see some PAGEIOLATCH_* waits, but if you’re frequently seeing them with wait times consistently above 10 milliseconds and you’re experiencing some type of latency, it suggests that the I/O subsystem is under pressure. Conversely, if you see many brief waits, you may be affected by increased I/O activity.

查詢正在等待對頁面的獨佔寫入訪問，以便將數據添加到頁面，可是該頁面當前不在內存中，必須從磁盤加載。

閂鎖是SQL Server 內部進程用於管理對內存中頁面緩衝區的訪問的輕量級、不可配置的鎖。當SQL Server必須將磁盤中的頁面讀取到內存緩衝區中或從緩衝區中讀取到磁盤時，它必須在進程進行時將閂鎖放在緩衝區頁面上。

看到一些PAGEIOLATCH_ *等待是很正常的，可是若是您常常看到它們的等待時間始終超過10毫秒，而且遇到某種類型的延遲，則代表I/O子系統面臨壓力。相反，若是您看到許多短暫的等待，則可能會受到I/O活動增長的影響。