Hello,
Does innodb_flush_log_at_trx_commit = 1 or 2 make a busy mysql server
bad performance?
We found that setting it to 0 will make disk IO decrease a lot.
Thanks.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org
Setting this option is a trade-off between your durability requirement
and performance requirement.
http://dev.mysql.com/doc/refman/5.1/en/innodb-parameters.htm l#sysvar_innodb_flush_log_at_trx_commit
0 gives best performance (write + flush once every second). 1 gives best
durability (write + flush after each commit). 2 writes the log buffer to
the log file at every commit, but flush it once every second.
On 10/16/2010 05:03 PM, short cutter wrote:
> Hello,
>
> Does innodb_flush_log_at_trx_commit = 1 or 2 make a busy mysql server
> bad performance?
> We found that setting it to 0 will make disk IO decrease a lot.
>
> Thanks.
>
>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org