diskpagebuffer table provides statistics
about disk page buffer usage by MySQL Cluster Disk Data tables.
The following table provides information about the columns in
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
|integer||The data node ID|
|integer||Number of pages written to disk.|
|integer||Number of pages written by local checkpoints.|
|integer||Number of pages read from disk|
|integer||Number of page writes waiting for log to be written to disk|
|integer||Number of requests for pages that were available in buffer|
|integer||Number of requests that had to wait for pages to become available in buffer|
|integer||Number of requests that had to be read from pages on disk (pages were unavailable in buffer)|
You can use this table with MySQL Cluster Disk Data tables to
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
the total number of reads using a query such as this one, which
obtains this ratio as a percentage:
SELECT node_id, 100 * page_requests_direct_return / (page_requests_direct_return + page_requests_wait_io) AS hit_ratio FROM ndbinfo.diskpagebuffer;
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 | +---------+-----------+ 4 rows in set (0.00 sec)
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
needs to be increased in the
A change in
requires a rolling restart of all of the cluster's data
nodes before it takes effect.