MySQL Forums
Forum List  »  Performance

Re: Poor performance of MySQL 5.5
Posted by: Vladislav Vaintroub
Date: June 11, 2011 07:30PM

in case you do many insert outside of transaction, innodb_flush_log_at_trx_commit=1 will force all tiny log records directly to the disk. Unless you're application is processing something extremely important like credit cards or so where in no case you can report success until the data hit stable media, you can almost safely use innodb_flush_log_at_trx_commit=2. Data reaches the disk platters safely after every second, so you can lose as much as last second of your operation if OS crashes.

Also ensure write cache on the disk is enabled. If not, then every write operation (even those for which direct write is not important for transactional integrity) will go directly to the disk.

Options: ReplyQuote

Written By
May 23, 2011 04:43AM
May 24, 2011 08:14AM
May 25, 2011 10:40AM
May 31, 2011 09:03AM
June 03, 2011 09:33AM
June 03, 2011 07:13PM
Re: Poor performance of MySQL 5.5
June 11, 2011 07:30PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.