Bug #53866 Manual Bug: enabling binary log "makes performance about 1% slower."
Submitted: 20 May 2010 18:23 Modified: 21 May 2010 15:56
Reporter: Morgan Tocker Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.1 OS:Any
Assigned to: Paul DuBois CPU Architecture:Any

[20 May 2010 18:23] Morgan Tocker
Description:
From the manual:
http://dev.mysql.com/doc/refman/5.1/en/binary-log.html

"Running a server with binary logging enabled makes performance about 1% slower. However, the benefits of the binary log in allowing you to set up replication and for restore operations generally outweigh this minor performance decrement."

I don't dispute that we should all have binary logging enabled, but quoting percentages like 1% is probably dangerous.  Because of broken group commit support (BUG 13669), it's a lot more than 1% on a server without a raid controller + BBU.

How to repeat:
See: http://www.mysqlperformanceblog.com/2006/05/19/group-commit-and-xa/ for performance differences.

It's not completely fixed in the plugin release, even though the bug is closed.

Suggested fix:
Change to something like:

"Enabling the binary log does result in a slight drop in performance.  However, the ..."
[20 May 2010 18:47] MySQL Verification Team
Thank you for the bug report.
[21 May 2010 15:56] Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.