I have been working with Peter in preparation for the talk comparing the optimizer enhancements in MySQL 5.6 and MariaDB 5.5. We are taking a look at and benchmarking optimizer enhancements one by one. So in the same way this blog post is aimed at a new optimizer enhancement Index Condition …
Post: Index Condition Pushdown in MySQL 5.6 and MariaDB 5.5 and its performance impact
March 12, 2012 By 12 Comments
Post: MySQL 5.5.8 and Percona Server: being adaptive
December 20, 2010 By 25 Comments
…. This method requires setting innodb_flush_neighbor_pages=0 , to disable flushing of neighborhood pages (not available in MySQL 5.5…_method = O_DIRECT innodb_read_ahead = none innodb_flush_neighbor_pages = 0 innodb_write_io_threads=8 innodb_read_io_threads=8 innodb…
Comment: read_ahead (disabled) as steroid
May 13, 2009 By 4 Comments
Should read_ahead always be disabled then to improve performance? What are the pros and cons?
Post: Benchmarking single-row insert performance on Amazon EC2
May 16, 2012 By 17 Comments
…_capacity = 800 innodb_read_io_threads = 8 innodb_write_io_threads = 4 innodb_file_per_table = 1 ## Disabling query cache query_cache… downward spikes in performance. Other then that, I have also disabled query cache to avoid contention caused by query cache on… I was mostly concerned with write performance, so I went ahead to choose a table structure with no secondary indexes. Other…
Post: Tokyo Tyrant - The Extras Part II : The Performance Wall
November 11, 2009 By 3 Comments
…   As fast as any application is, as you read off disk opposed to memory performance is going to drop… this I went ahead an mounted the FS with my data files with the sync option which effectively disables the FS cache… here is we are actually bottlenecking on writes and not reads. You see without the FS cache to buffer the…
