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.
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.
Subject
Views
Written By
Posted
15814
May 23, 2011 04:43AM
5007
May 24, 2011 08:14AM
5021
May 25, 2011 04:10AM
5111
May 25, 2011 10:40AM
3588
May 31, 2011 07:15AM
3267
May 31, 2011 09:03AM
3001
May 31, 2011 11:15AM
3646
June 03, 2011 01:44AM
2456
June 03, 2011 02:20AM
3871
June 03, 2011 09:33AM
2758
June 03, 2011 11:25AM
4259
June 09, 2011 05:36AM
2377
June 03, 2011 11:38AM
2423
June 03, 2011 07:13PM
Re: Poor performance of MySQL 5.5
2357
June 11, 2011 07:30PM
2047
June 11, 2011 07:32PM
2618
June 12, 2011 10:09AM
2269
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.