Alexander, ----- Original Message ----- From: "Varshavchick Alexander" <[EMAIL PROTECTED]> To: "Heikki Tuuri" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, September 05, 2002 6:51 PM Subject: Re: Performance Problems with InnoDB Row Level Locking...
> Heikki, one little question - is it a mistype, or can a flush log interval > duration be controlled by this option? The value should only be 0 or 1 as > the documentation says... there is a new value 2 introduced in 3.23.52: " A new setting innodb_flush_log_at_trx_commit=2 makes InnoDB to write the log to the operating system file cache at each commit. This is almost as fast as the setting innodb_flush_log_at_trx_commit=0, and the setting 2 also has the nice feature that in a crash where the operating system does not crash, no committed transaction is lost. If the operating system crashes or there is a power outage, then the setting 2 is no safer than the setting 0. " 0 = write to log file once per second 1 = write to log file and flush the log to disk at every commit 2 = write to log file at every commit, but only flush to disk once per second I think 2 will be the best setting for most high-end users. > On Thu, 5 Sep 2002, Heikki Tuuri wrote: > > > You can try setting > > > > innodb_flush_log_at_trx_commit=2 > > > > if you can afford losing some last transactions in a power outage or an > > operating system crash. > > > > ---- > Alexander Varshavchick, Metrocom Joint Stock Company > Phone: (812)118-3322, 118-3115(fax) Best regards, Heikki Tuuri Innobase Oy --- InnoDB - transactions, hot backup, and foreign key support for MySQL See http://www.innodb.com, download MySQL-Max from http://www.mysql.com --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
