…mysql socket=/var/lib/mysql/mysql.sock user=justin innodb_buffer_pool_size=64G innodb_log_file_size=4G innodb_file_per_table innodb_stats_on_metadata=off innodb_file_format=barracuda innodb_log_buffer_size=32M innodb…
Post: Percona Server 5.1.69-14.7 now available: A drop in replacement for MySQL
June 10, 2013 By 3 Comments
…MySQL account owner could perform…log reads needlessly, potentially limiting performance on write-intensive workloads. Bug fixed #1171699. Missing path separator between the directory and file name components in a bitmap file name could stop the server starting if the innodb…zero-size bitmap file …
Post: Percona Server 5.6.11-60.3 first Release Candidate now available
June 3, 2013 By 3 Comments
… align=”alignright” width=”247″] Percona Server for MySQL version 5.6.11-60.3[/caption…performance for high levels of concurrency. Bug fixed #1185686. Under very rare circumstances, deleting a zero-size bitmap file… #1185040. The INNODB_CHANGED_PAGES table couldn’t be queried if the log tracker wasn’t…
Comment: How to calculate a good InnoDB log file size
May 21, 2013 By 38 Comments
…: http://dev.mysql.com/doc/refman/5.5/en/innodb-performance-recovery.html “If you kept the size of your redo log files artificially low because recovery took a long time, you can consider increasing the file size.”
Post: Benchmarking Percona Server TokuDB vs InnoDB
May 7, 2013 By 32 Comments
…innodb_log_buffer_size = 256M innodb_flush_log_at_trx_commit = 1 innodb_buffer_pool_size = 36G innodb_log_file_size = 4G innodb_log_files_in_group = 2 innodb_log_block_size=4096 #####plugin options innodb…
Post: MySQL and Percona Server in LinkBench benchmark
May 8, 2013 By 18 Comments
…innodb_log_file_size = 2000M innodb_log_files_in_group = 2 innodb_flush_log_at_trx_commit = 1 innodb_log_buffer_size=128M innodb_max_dirty_pages_pct=80 innodb_file_format=barracuda innodb_file_per_table innodb…
Post: More on MySQL transaction descriptors optimization
April 26, 2013 By Leave a Comment
…in the first two cases Percona Server performance is even slightly ahead of MySQL 5.6.10, but nothing …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_log_files_in_group = 2 innodb_file…
Post: Virident vCache vs. FlashCache: Part 2
May 17, 2013 By 3 Comments
…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_at_trx_commit = 1 innodb_log_file_size = 1G innodb_log_files…
Post: Choosing proper innodb_log_file_size
July 3, 2006 By 12 Comments
… to Innodb tables decent size of innodb_log_file_size is important for MySQL Performance. However setting it too large will increase recovery time, so in case of MySQL… on recovery and why large innodb_log_file_size slows down recovery. During startup after crash Innodb scans log files to find log records which only have been…
Post: Effect from innodb log block size 4096 bytes
January 3, 2011 By 19 Comments
…size=26G innodb_data_file_path=ibdata1:10M:autoextend innodb_file_per_table=1 innodb_flush_log_at_trx_commit=2 innodb_log_buffer_size=8M innodb_log_files_in_group=2 innodb_log_file_size=4G innodb…
