Re: Poor performance of MySQL 5.5
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.
Make sure write cache on the disk is enabled. If not, then every write operation (even those that are not cruicial for transactional integrity to be processed immediately) will go directly to the disk.
Subject
Views
Written By
Posted
15395
May 23, 2011 04:43AM
4917
May 24, 2011 08:14AM
4914
May 25, 2011 04:10AM
4975
May 25, 2011 10:40AM
3500
May 31, 2011 07:15AM
3190
May 31, 2011 09:03AM
2899
May 31, 2011 11:15AM
3545
June 03, 2011 01:44AM
2374
June 03, 2011 02:20AM
3756
June 03, 2011 09:33AM
2654
June 03, 2011 11:25AM
4151
June 09, 2011 05:36AM
2301
June 03, 2011 11:38AM
2340
June 03, 2011 07:13PM
2270
June 11, 2011 07:30PM
Re: Poor performance of MySQL 5.5
1966
June 11, 2011 07:32PM
2537
June 12, 2011 10:09AM
2173
June 15, 2011 01:08PM
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.