June 20, 2013

Post: MySQL and the SSB - Part 2 - MyISAM vs InnoDB low concurrency

… tmpdir=/dev/shm innodb_undo_logs=32 innodb_old_blocks_time=0 table_open_cache=2048 table_definition_cache=16384 innodb_flush_method=O_DIRECT key_buffer_size=10G # Disabling symbolic-links is recommended to prevent assorted security risks symbolic-links=0 innodb

Post: Percona Server 5.1.69-14.7 now available: A drop in replacement for MySQL

… if the XtraDB changed page tracking was enabled and variable innodb_flush_method was set to ALL_O_DIRECT. Bug fixed #1131949. Fixed… if a bitmap file I/O error occurs after an INNODB_CHANGED_PAGES query started returning data to indicate an incomplete… if changed page tracking is enabled. Bug fixed #1184517. The INNODB_CHANGED_PAGES table couldn’t be queried if the log…

Post: Benchmarking Percona Server TokuDB vs InnoDB

… SSD innodb_flush_neighbor_pages = none innodb_adaptive_flushing_method = keep_average innodb_file_per_table = true innodb_data_file_path = ibdata1:100M:autoextend innodb_flush_method = O_DIRECT innodb_log_buffer_size = 256M innodb_flush_log…

Post: Virident vCache vs. FlashCache: Part 2

innodb options innodb_file_format = barracuda innodb_buffer_pool_size = 4G innodb_file_per_table = true innodb_data_file_path = ibdata1:100M innodb_flush_method = O_DIRECT innodb_log_buffer_size = 128M innodb_flush_log…

Post: MySQL and Percona Server in LinkBench benchmark

innodb_buffer_pool_size = 30G innodb_flush_method = O_DIRECT innodb_log_file_size = 2000M innodb_log_files_in_group = 2 innodb_flush_log_at_trx_commit = 1 innodb_log_buffer_size=128M innodb

Post: More on MySQL transaction descriptors optimization

innodb_status_file=0 innodb_data_file_path=ibdata1:100M:autoextend innodb_flush_log_at_trx_commit = 2 innodb_flush_method = O_DIRECT innodb_log_buffer_size = 16M innodb_buffer_pool_size = 52G innodb_log_file_size = 2000M innodb

Post: Optimizing InnoDB for creating 30,000 tables (and nothing else)

…… I can set some InnoDB options! I’m going to try the obvious first: innodb-flush-method, sync-frm and innodb-flush-log-at-trx-commit. There is an undocumented option for innodb-flush-method called “nosync” that is meant to not flush

Post: Disaster: MySQL 5.5 Flushing

InnoDB configured for this hardware innodb_flush_log_at_trx_commit = 2 innodb_flush_method = O_DIRECT innodb_log_buffer_size = 16M innodb_buffer_pool_size = 52G innodb_log_file_size = 1900M innodb

Post: Benchmarks of new innodb_flush_neighbor_pages

… on innodb_flush_neighbor_pages. By default InnoDB flushes so named neighbor pages, which really are not neighbors. Say we want to flush page P. InnoDB… intention to flush as many pages as possible in singe sequential write. So we added new innodb_flush_neighbor_pages=cont method, with it…

Post: Adaptive flushing in MySQL 5.6

… MySQL options: innodb_file_per_table = true innodb_data_file_path = ibdata1:100M:autoextend innodb_flush_method = O_DIRECT innodb_log_buffer_size = 256M innodb_flush_log_at_trx_commit = 2 innodb_buffer_pool_size = 150G innodb_log_file_size = 4G innodb