June 19, 2013

Comment: How to calculate a good InnoDB log file size

It seems that in 5.5 the second log file is touched even if a rotation has not occurred, that …://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: MySQL and Percona Server in LinkBench benchmark

…5 outperforms MySQL in about 2x times. Both MySQL 5.5.30 and MySQL 5.6…. in LRU_scan. I tried to increase innodb_lru_scan_depth variable to …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

Post: Benchmarking Percona Server TokuDB vs 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

Post: Choosing proper innodb_log_file_size

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… with 1GB log files and 2GB and see if there is any performance benefit. After certain size increasing log file size do not dramatically increase performance,…

Post: Should MySQL update the default innodb_log_file_size?

… default storage engine in MySQL, is it time to update the default configuration for the InnoDB log file size (innodb_log_file_size) setting? In general, there… production installation. MySQL 5.5 increased the default buffer pool size to something more sane (128MB instead of 8MB), but the log file size remains at…

Post: MySQL 5.5 and MySQL 5.6 default variable values differences

…_LOG_FILE_SIZE | 5242880 | 50331648 | | BASEDIR | /mnt/nfs/dist/5.5.30 | /mnt/nfs/dist/5.6.10 | | BACK_LOG | 50 | 80 | | OPEN_FILES_LIMIT… disabled by default in MySQL 5.6 Welcome to much faster information_schema queries! innodb_log_file_size – default has been increased from 5MB to…

Post: Measuring the amount of writes in InnoDB redo logs

… InnoDB log file size is key to InnoDB write performance. This can be done by measuring the amount of writes in the redo logs… that Innodb_os_log_written is the number of bytes written to the log file The LSN is an arbitrary, ever-increasing value [that] represents a point in time corresponding to operations recorded in the redo log

Post: Effect from innodb log block size 4096 bytes

…innodb-log-block-size=4096 in Percona Server to get better throughput, but later Dimitri in his article MySQLfile_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… run it is 49130.13 NOTPM, that is increase is 1.28x, and I can’t …

Post: MySQL 5.5.8 - in search of stability

… in MySQL 5.5.8. Let’s see what we can do with them. Article [1] also advises that innodb_log_file_sizeincrease it to 70% ? It seems 70% is too big, and now we again hit the limit set by innodb_log_file_size… still innodb_log_file_size. To prove it, I took Percona Server based on 5.5.8 and ran it in MySQL mode (that…

Post: What to tune in MySQL Server after installation

… question during Interview for people to work as MySQL DBAs or be involved with MySQL Performance in some way is to ask… needs. innodb_log_file_size Very important for write intensive workloads especially for large data sets. Larger sizes offer better performance but increase recovery times…