Re: innodb_flush_log_at_trx_commit

2010-10-16 Thread Sander de Bruijne
+ 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

innodb_flush_log_at_trx_commit

2010-10-16 Thread short cutter
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

Re: what should be the value of innodb_flush_log_at_trx_commit

2006-08-28 Thread Visolve DB Team
Hi, InnoDB provides MySQL with a transaction-safe (ACID compliant) storage engine that has commit, rollback, and crash recovery capabilities. MyISAM, the default storage engine. Unless compiled with InnoDB, MySQL is not ACID compliant. When innodb_flush_log_at_trx_commit =0 the log buffer

what should be the value of innodb_flush_log_at_trx_commit

2006-08-28 Thread Ratheesh K J
hello all, We do not run transactions at all on our db. All our queries are autocommit. So what should be the value set to this variable : innodb_flush_log_at_trx_commit We currently have it set to 1 and all our tables are Innodb. Since we are not running any transactions at all, is it better

InnoDB : innodb_flush_log_at_trx_commit=0

2004-01-31 Thread DUFOUR Geoffrey
Hello, As far as I understand, setting innodb_flush_log_at_trx_commit to 0 could lead to several problems (data loss ?, ...). Can you tell me more about it ? Regards. Geoffrey Dufour -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http

Re: innodb_flush_log_at_trx_commit

2002-06-04 Thread ritu singla
Jeremy, do we have the control as to WHEN to update the actual tables??? Thanx.. Ritu Singla --- Jeremy Zawodny <[EMAIL PROTECTED]> wrote: > On Mon, Jun 03, 2002 at 07:07:29AM +0100, ritu > singla wrote: > > Hello, > > > > in InnoDB tables in MySQL, if > &g

Re: innodb_flush_log_at_trx_commit

2002-06-02 Thread Jeremy Zawodny
On Mon, Jun 03, 2002 at 07:07:29AM +0100, ritu singla wrote: > Hello, > > in InnoDB tables in MySQL, if > innodb_flush_log_at_trx_commit is set to 1, then on > COMMIT, the buffer log is flushed to disk log... Right. > or the changes are reflected in the disk copy of the dat

innodb_flush_log_at_trx_commit

2002-06-02 Thread ritu singla
Hello, in InnoDB tables in MySQL, if innodb_flush_log_at_trx_commit is set to 1, then on COMMIT, the buffer log is flushed to disk log...or the changes are reflected in the disk copy of the database??? i mean what is flushed, the buffer-pool that contains data and indexes or the log-buffer

Re: about innodb_flush_log_at_trx_commit

2002-01-30 Thread Jeremy Zawodny
On Wed, Jan 30, 2002 at 03:06:36PM -0800, Joseph Drozdik wrote: > Hi all, > > I've been looking at the performance of mysql using innodb tables > and I've noticed that I can get a huge benifit by setting > innodb_flush_log_at_trx_commit = 0. The documentation warns me th

about innodb_flush_log_at_trx_commit

2002-01-30 Thread Joseph Drozdik
Hi all, I've been looking at the performance of mysql using innodb tables and I've noticed that I can get a huge benifit by setting innodb_flush_log_at_trx_commit = 0. The documentation warns me that I can loose a couple of seconds of transactions in system crash if I do this. It se