…. Percona Server 5.5 outperforms MySQL in about 2x times. Both MySQL 5.5.30 and MySQL 5.6.11 demonstrate notable drops…_in_group = 2 innodb_flush_log_at_trx_commit = 1 innodb_log_buffer_size=128M innodb_max_dirty_pages_pct=80 innodb_file… #56only loose-innodb_flush_neighbors=0 loose-metadata_locks_hash_instances=256 innodb_buffer_pool_instances=16 # MySQL 5.5 and 5…
Post: Virident vCache vs. FlashCache: Part 2
May 17, 2013 By 3 Comments
… dirty-page-threshold flushing, which kicks in at a given level and then attempts to flush as quickly as possible to bring the dirty pages…time=7200 –max-requests=0 –percentile=95 \ –mysql-user=root –mysql-socket=/tmp/mysql.sock –mysql-table-engine=innodb \ –oltp-read-only=off …
Post: Virident vCache vs. FlashCache: Part 1
May 16, 2013 By 3 Comments
… to conduct some benchmarks for the use case where the MySQL working set is significantly larger than the InnoDB buffer pool… caching sequential IO, adjusting the dirty page threshold, flushing the cache on demand, or having a time-based cache flushing mechanism, but some of… it here. The vCache manual indicates that “flush period” specifies the time after which dirty blocks will be written to the backing…
Post: Benchmarks of new innodb_flush_neighbor_pages
January 17, 2012 By 8 Comments
… to flush page P. InnoDB is looking in an area of 128 pages around page P, and flushes all the pages in that area that are dirty… dot is a page that does not need flushing, each “D” is a dirty page that InnoDB will flush, and P is our page. So, as… have longer and deeper periods when MySQL stuck in flushing, and in such cases, the innodb_flush_neighbor_pages=cont only helps to relief…
Post: Ultimate MySQL variable and status reference list
January 8, 2011 By 4 Comments
…the amazing MySQL manual, especially the option and variable … federatedblogpercona.commanual flushblogpercona.commanual Flush_commandsblogpercona.commanual flush_timeblogpercona.commanual foreign_key_…_log_writesblogpercona.commanual innodb_max_dirty_pages_pctblogpercona.commanual innodb_max_purge_…
Post: Multiple purge threads in Percona Server 5.1.56 and MySQL 5.6.2
May 3, 2011 By 13 Comments
…_size=1900M innodb_flush_log_at_trx_commit=2 innodb_doublewrite=1 innodb_flush_method=O_DIRECT innodb_max_dirty_pages_pct=80 innodb… to not to penalize further TPS. MySQL 5.6.2 Results Now let’s test MySQL 5.6.2. It is important… is a quick and dirty change and by no means a replacement to proper future 5.6 tuning. MySQL 5.6.2…
Post: Why Swapping is bad for MySQL Performance ?
January 18, 2010 By 11 Comments
… get page being cached read from the hard drive to the cache. This gives us 3 IOs instead of one. Nice 
Flushing dirty pages or even discarding the page will cause extra IO slowing things down. Skewing… consumption spike you may prefer to see slowdown instead of MySQL being killed because of out of memory but do react…
Post: The relationship between Innodb Log checkpointing and dirty Buffer pool pages
February 17, 2012 By 10 Comments
… dirty buffer flushing also doesn’t scale well on high io subsystems, it effectively just doubles the dirty buffer flushing per second when the % dirty pages… run any kind of production MySQL server, you should be monitoring your Checkpoint age and your Innodb dirty pages and try to see…
Post: MySQL 5.5.8 - in search of stability
January 3, 2011 By 11 Comments
… innodb_flush_neighbor_pages=0. Okay, we are back to a stable level. Checkpoint age is also back to 3000MB, and dirty pages are…=500 innodb_max_dirty_pages_pct = 60 innodb_purge_threads=1 innodb_adaptive_flushing=0 innodb_doublewrite=1 innodb_flush_neighbor_pages=0 innodb_adaptive… try to get stable throughput in MySQL 5.5.8 by playing with innodb_max_dirty_pages_pct and innodb_io_capacity and…
Post: Different flavors of InnoDB flushing
January 13, 2011 By 9 Comments
… page (this is what LRU stands for). The flush list is used when the percentage of dirty pages reaches innodb_max_dirty_pages_pct, or for flushing…_dirty_pages_pct=75, and with 52GB we are reaching the 75% maximum for dirty pages. How can you detect in regular MySQL that your flushing… are flush list bound, then for MySQL 5.1/InnoDB-plugin or MySQL 5.5 the setting of innodb_adaptive_flushing, innodb_max_dirty_pages_pct…
