May 24, 2012

Comment: How to change innodb_log_file_size safely

…’/var/lib/mysql/mysql.sock’ port: 3306 Source distribution Also, I don’t see how MySQL could be using any other conf file other….old /etc/my.cnf.rpmnew [root@tstlx1 mysql]# cat /etc/my.cnf | grep log_file # Set .._log_file_size to 25 % of buffer pool size innodb_log_file_size = 64M [root@tstlx1 mysql

Post: Troubleshooting MySQL Memory Usage

MySQL to use reasonable global buffers, such as innodb_buffer_size, key_buffer_size etc, you have reasonable amount of connections but yet MySQLset (0.00 sec) Innodb Memory Usage Finally it is often helpful to check how much memory InnodbFile

Post: How to calculate a good InnoDB log file size

how to choose a good log file size!  So I thought I’d clarify it a little. The basic point is that your log file needs toto 128 for good measure. Since there are two log files by default, divide that in half, and now you can set innodb_log_file_size

Post: Choosing proper innodb_log_file_size

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

Post: MySQL 5.5.8 - in search of stability

to increase it to 70% ? It seems 70% is too big, and now we again hit the limit set by innodb_log_file_sizeMySQL 5.5.8 by tuning innodb_max_dirty_pages_pct and innodb_io_capacity; but the limiting factor is still innodb_log_file_size. To

Post: Analyzing the distribution of InnoDB log file writes

to InnoDB‘s log files. On a high-traffic commodity MySQL server running Percona XtraDB for a gaming workload (mostly inserts to the “moves” table), I used strace to gather statistics about how the log file writes are distributed in terms of write size. InnoDB writes to the log files

Post: How to estimate time it takes Innodb to Recover ?

Innodb talks and during consulting engagements. It is well known to get better performance you should normally set innodb_log_file_sizelog file time may have recovery time of 5-10 minutes. To understand things affecting recovery time you better to understand how Innodb recovery works. When Innodb

Post: How to Monitor MySQL with Percona's Nagios Plugins

file and directory within its data directory. InnoDB is getting stuck, has long-running transactions, or other problems. The pmp-check-mysql-innodbto handle max_connections problems (the use of fixed-size connection pooling, for example, which can sometimes require application downtime to

Post: What's required to tune MySQL?

to deliver huge wins. If MySQLto make. A few of the common ones I see are not configuring the InnoDB buffer pool size or log file size, and not using InnoDBto unlikely circumstances, I sometimes see unlikely settings, such as making the sort buffer size much too large (a gigabyte comes to

Post: How Percona does a MySQL Performance Audit

… know how to read these, there’s a full explanation in our book, High Performance MySQL 2nd Edition…to miss, as is the absence of innodb_log_file_size. I won’t give you a full rundown over every option in the file…s hard to read. If the InnoDB buffer pool is set to 22GB, it’s much easier to see 22GB …