Percona's MySQL & InnoDB performance and scalability blog
… 5.5.30 and MySQL 5.6.10 with no tuning whatsoever (with one exception that I’ll explain below) – the… that table by querying the various I_S.INNODB_FT_* tables. In particular, the INNODB_FT_CONFIG table is supposed to “display… global innodb_ft_aux_table=’test/dir_test_innodb‘; mysql> set global innodb_optimize_fulltext_only=1; mysql> select * from information_schema.innodb_ft…
… be tuned for “innodb_doublewrite = false” only. (cause too much flushing for “innodb_doublewrite = true”) “innodb_adaptive_checkpoint = reflex” and “adaptive_flushing” need tuning innodb_io_capacity properly. (The result is based on proper value “innodb_io…
… down the to the tablespace. If Innodb stops (read: crashes) with dirty buffer pool pages, Innodb recovery must be done to rebuild… pages under control, and before the Innodb plugin this was really the only way to tune dirty buffer flushing. However, I have…/or use the global tablespaces) *cough ext3 cough*. innodb_adaptive_flushing: An Innodb plugin/5.5 setting that tries to be smarter…
… serendipitous call (thanks!) yesterday asking what would be needed to tune[1] a database for better performance. It is a question… see are not configuring the InnoDB buffer pool size or log file size, and not using InnoDB. If your server really hasn… configuration alone. [1] I prefer to avoid the word “tuning,” because database tuning is an activity that can be done endlessly, with…
… in MyISAM but would not fit to Innodb, though this is an exception. Space Innodb Tables tend to be larger. Again converting… do not want to try to run Innodb or XtraDB with them. Second Innodb is tuned to be ACID by default – if you… innodb_flush_log_at_trx_commit, innodb_buffer_pool_size and innodb_log_file_size. There are a lot more options for fine tuning…
… Pages for allocating Innodb Buffer Pool and few other buffers, which may have other performance benefits as well. Tuning your VM to… while Innodb can simply discard that pages in case of memory pressure. But what is more important Innodb algorithms are finely tuned with consideration what is in memory and what is on disk, for example when Innodb tries…
… used to tune innodb_thread_concurrency. I fact it would be great if I could get rid of this kind of “tuning“. It sucks:-) So when you say it *was* limited Im wouldnt bother with it anymore *yippi*. Would you say innodb_thread…
… 5.5.8 by tuning innodb_max_dirty_pages_pct and innodb_io_capacity; but the limiting factor is still innodb_log_file_size… innodb_write_io_threads = 16 innodb_io_capacity=500 innodb_max_dirty_pages_pct = 60 innodb_purge_threads=1 innodb_adaptive_flushing=0 innodb_doublewrite=1 innodb_flush_neighbor_pages=0 innodb…
… tickets to use. Innodb tries to limit thread concurrency allowing only innodb_thread_concurrency threads to run inside Innodb kernel at the same… thread is not runniing inside innodb kernel status could be “waiting in InnoDB queue” or “sleeping before joining InnoDB queue”. Latest one is… is smaller than allocated buffer pool size so you can tune it down. Even if free pages is zero as in…
… ~ 10GB of data, 12G innodb_buffer_pool_size, 1G innodb_log_file_size), MySQL 5.5.10 with innodb_adaptive_flushing=ON (default… increase innodb_io_capacity and decrease innodb_max_dirty_pages_pct so as to have fewer dirty pages. But I call that tuning… jumps in flushing pages. Make the algorithm independent of innodb_io_capacity and innodb_max_dirty_pages_pct. (This is important for…
Copyright © Percona LLC • Contact Us • MySQL and InnoDB are trademarks of Oracle Corp.