I’ve been working a lot with xtradb versions of mysql over the last year, and more and more have begun to attempt to leverage the information_schema instrumentation that has been put in place.
Today, I went into a system with this install (admittedly a very recent one)
Server version: 5.1.51-rel11.5-log Percona Server (GPL), 11.5, Revision 132
Having been considering upgrading RAM on the server, I went to look at how the innodb_buffer_pool was currently being used. The information_schema tables seem to have changed dramatically, particularly around the innodb_buffer_pool related tables found
here.
At this point, I’m at a loss of how to get information on which tables/indexes are using space (and how much) in the buffer pool. I had used INNODB_BUFFER_POOL_PAGES_INDEX to do this in the past. Hopefully documentation will be forthcoming on the new table structures. Admittedly, I haven’t dug too deeply into the new structures (since they are not documented). I’m curious if anyone else has worked with the newer table structures:
INNODB_BUFFER_POOL_PAGES_INDEX\G
*************************** 1. row ***************************
Table: INNODB_BUFFER_POOL_PAGES_INDEX
Create Table: CREATE TEMPORARY TABLE `INNODB_BUFFER_POOL_PAGES_INDEX` (
`index_id` bigint(21) unsigned NOT NULL DEFAULT ‘0’,
`space_id` bigint(21) unsigned NOT NULL DEFAULT ‘0’,
`page_no` bigint(21) unsigned NOT NULL DEFAULT ‘0’,
`n_recs` bigint(21) unsigned NOT NULL DEFAULT ‘0’,
`data_size` bigint(21) unsigned NOT NULL DEFAULT ‘0’,
`hashed` bigint(21) unsigned NOT NULL DEFAULT ‘0’,
`access_time` bigint(21) unsigned NOT NULL DEFAULT ‘0’,
`modified` bigint(21) unsigned NOT NULL DEFAULT ‘0’,
`dirty` bigint(21) unsigned NOT NULL DEFAULT ‘0’,
`old` bigint(21) unsigned NOT NULL DEFAULT ‘0’,
`lru_position` bigint(21) unsigned NOT NULL DEFAULT ‘0’,
`fix_count` bigint(21) unsigned NOT NULL DEFAULT ‘0’,
`flush_type` bigint(21) unsigned NOT NULL DEFAULT ‘0’
) ENGINE=MEMORY DEFAULT CHARSET=utf8
Want to talk with an expert? Schedule a call with our team to get the conversation started.
No comments