May 24, 2012

Post: Troubleshooting MySQL Memory Usage

Buffer pool size 7864319 Buffer pool size, bytes 128849002496 Free buffers 1 Database pages 8252672 Old database pages 3046376 Modified db pages 23419 I’m using the information from

Post: How to decrease InnoDB shutdown times

… server running InnoDB takes a long time to shut down. The usual culprit is flushing dirty pages from the buffer pool. These are pages that have been modified in memory, but not on disk. If you kill the server…

Post: The relationship between Innodb Log checkpointing and dirty Buffer pool pages

from the BUFFER POOL AND MEMORY section of SHOW ENGINE INNODB STATUS: Database pages 65530 … Modified db pages 3 So we have 3 pages that have modified

Post: InnoDB Flushing: Theory and solutions

The two most important parameters for InnoDB performance are innodb_buffer_pool_size and innodb_log_file_size. InnoDBthe oldest modified non-flushed page. Checkpoint_age is located somewhere between 0 and innodb_log_file_size. Point 0 means there are no modified pages

Post: The performance effects of new patches

the storage. main common settings innodb_buffer_pool_size = 2048M innodb_thread_concurrency = 0 innodb_max_dirty_pages_pct = 70 innodb_flush_method = O_DIRECT The next graphs show the

Post: SHOW INNODB STATUS walk through

innodb_flush_log_at_trx_commit value your log writes may be more or less expensive. If innodb_flushpages in buffer pool, number of pages free, pages allocated by database pages and dirty pages. From these values you can learn if your buffer

Post: Heikki Tuuri Innodb answers - Part I

… this data and allows the user to tune the checkpointing values. HT: Hmm… we could tune the way InnoDB does the buffer pool flush. I think Yasufumi… than flush 10 non sequential pages from it which were modified. Q21: What’s the status of INNODB in 5.1.x? Specifically: What’s the current…

Post: Innodb Fuzzy checkpointing woes

the pages which basically corresponds to age of unflushed pages. In such case current implementation works just fine – Innodb flushflush and Innodb might end up flushing most of buffer pool pages.      Now as the pages are flushed they get modified

Post: Which adaptive should we use?

InnoDB has 2 limits for unflushed modified blocks in the buffer pool. The one is from physical size of the buffer pool. And the another one is oldness of the

Post: Disaster: MySQL 5.5 Flushing

… case from the Oracle/MySQL engineers is to decrease “innodb_max_dirty_pages_pct”, this way InnoDB will try to keep less dirty pages in buffer pool… this may help ? InnoDB flushing may kick-in faster, and do not allow to have a lot of modified pages in buffer pool. Let’s…