Rechercher dans le manuel MySQL
22.5.10.20 The ndbinfo diskpagebuffer Table
The diskpagebuffer
table provides statistics
about disk page buffer usage by NDB Cluster Disk Data tables.
The following table provides information about the columns in
the diskpagebuffer
table. For each column,
the table shows the name, data type, and a brief description.
Additional information can be found in the notes following the
table.
Table 22.394 Columns of the diskpagebuffer table
Column Name | Type | Description |
---|---|---|
node_id |
integer | The data node ID |
block_instance |
integer | Block instance |
pages_written |
integer | Number of pages written to disk. |
pages_written_lcp |
integer | Number of pages written by local checkpoints. |
pages_read |
integer | Number of pages read from disk |
log_waits |
integer | Number of page writes waiting for log to be written to disk |
page_requests_direct_return |
integer | Number of requests for pages that were available in buffer |
page_requests_wait_queue |
integer | Number of requests that had to wait for pages to become available in buffer |
page_requests_wait_io |
integer | Number of requests that had to be read from pages on disk (pages were unavailable in buffer) |
You can use this table with NDB Cluster Disk Data tables to
determine whether
DiskPageBufferMemory
is
sufficiently large to allow data to be read from the buffer
rather from disk; minimizing disk seeks can help improve
performance of such tables.
You can determine the proportion of reads from
DiskPageBufferMemory
to
the total number of reads using a query such as this one, which
obtains this ratio as a percentage:
The result from this query should be similar to what is shown here, with one row for each data node in the cluster (in this example, the cluster has 4 data nodes):
- +---------+-----------+
- | node_id | hit_ratio |
- +---------+-----------+
- | 5 | 97.6744 |
- | 6 | 97.6879 |
- | 7 | 98.1776 |
- | 8 | 98.1343 |
- +---------+-----------+
hit_ratio
values approaching 100% indicate
that only a very small number of reads are being made from disk
rather than from the buffer, which means that Disk Data read
performance is approaching an optimum level. If any of these
values are less than 95%, this is a strong indicator that the
setting for
DiskPageBufferMemory
needs to be increased in the config.ini
file.
A change in
DiskPageBufferMemory
requires a rolling restart of all of the cluster's data
nodes before it takes effect.
block_instance
refers to an instance of a
kernel block. Together with the block name, this number can be
used to look up a given instance in the
threadblocks
table. Using this
information, you can obtain information about disk page buffer
metrics relating to individual threads; an example query using
LIMIT 1
to limit the output to a single
thread is shown here:
- mysql> SELECT
- > node_id, thr_no, block_name, thread_name, pages_written,
- > pages_written_lcp, pages_read, log_waits,
- > page_requests_direct_return, page_requests_wait_queue,
- > page_requests_wait_io
- > FROM ndbinfo.diskpagebuffer
- *************************** 1. row ***************************
- node_id: 1
- thr_no: 1
- block_name: PGMAN
- thread_name: rep
- pages_written: 0
- pages_written_lcp: 0
- pages_read: 1
- log_waits: 0
- page_requests_direct_return: 4
- page_requests_wait_queue: 0
- page_requests_wait_io: 1
Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-mysql-cluster-ndbinfo-diskpagebuffer.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.