Hi Abdul,
When sync_binlog is set to 1, innodb fsyncs the binary log to
disk after every single write to binary log, but not in the case of
sync_binlog=0.
From MySQL manual:
<snip>
If the value of this variable is positive, the MySQL server synchronizes its
binary log to disk (fdatasync()) after every sync_binlog writes to this
binary log. Note that there is one write to the binary log per statement if
in autocommit mode, and otherwise one write per transaction. The default
value is 0 which does no sync'ing to disk. A value of 1 is the safest choice,
because in case of crash you lose at most one statement/transaction from the
binary log; but it is also the slowest choice (unless the disk has a
battery-backed cache, which makes sync'ing very fast). This variable was
added in MySQL 4.1.3.
</snip>
--Ravi
On Tuesday 11 April 2006 10:22, Mohammed Abdul Azeem wrote:
> Hi,
>
> I have a master/slave setup ( replication enabled ) for mysql in two
> different geographic locations ( one master/slave set up in each
> location). In one location i have configured the sync_binlog=1 . And the
> other location does not have the same.
>
> My problem is, when i run similar update processes on both the master
> servers, the server with sync_binlog=1 is very slower in terms of
> completing the update query as compared to the machine having
> sync_binlog=0.
>
> Is that a cause for slow performance ?
>
> Thanks in advance,
> Abdul.
>
> ________________________________________
> This email has been Scanned for Viruses!
> www.newbreak.com
>
> ========================================
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
