gian/phpmyadmin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Typo

Browse Source
This commit is contained in:
Marc Delisle 2011-11-02 15:25:58 -04:00
parent f0c58e2a59
commit 8d3bb76d26
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
libraries/advisory_rules.txt
View File

@ -421,7 +421,7 @@ rule 'Max InnoDB log size' [innodb_buffer_pool_size > 0 && innodb_log_file_size
innodb_log_file_size / (1024 * 1024)
value >= 128
The InnoDB log file size is inadequately large.
It is usually sufficient to set innodb_log_file_size to 25% of the size of {innodb_buffer_pool_size}. A very innodb_log_file_size slows down the recovery time after a database crash considerably. See also <a href="http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/">this Article</a>. You need to shutdown the server, remove the InnoDB log files, set the new value in my.cnf, start the server, then check the error logs if everything went fine. See also <a href="http://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">this blog entry</a>
It is usually sufficient to set innodb_log_file_size to 25% of the size of {innodb_buffer_pool_size}. A very big innodb_log_file_size slows down the recovery time after a database crash considerably. See also <a href="http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/">this Article</a>. You need to shutdown the server, remove the InnoDB log files, set the new value in my.cnf, start the server, then check the error logs if everything went fine. See also <a href="http://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">this blog entry</a>
Your absolute InnoD log size is %s MiB | round(value,1)
rule 'InnoDB buffer pool size' [system_memory > 0]