Bug #31876 InnoDB commit performance slow on Windows XP
Submitted: 26 Oct 2007 12:09 Modified: 25 Feb 2014 19:17
Reporter: Kristian Koehntopp Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S4 (Feature request)
Version:5.0.46 OS:Windows (Windows XP)
Assigned to: CPU Architecture:Any

File: Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

[26 Oct 2007 12:11] Kristian Koehntopp
Benchmark: 500 insert/commit pairs

Attachment: 500_inserts_mysql_with_create.txt (text/plain), 118.25 KiB.

[26 Oct 2007 12:12] Kristian Koehntopp
FileMon log at innodb_flush_log_at_trx_commit = 1

Attachment: binlog_off_trx_1.LOG (text/plain), 132.34 KiB.

[26 Oct 2007 12:12] Kristian Koehntopp
FileMon log at innodb_flush_log_at_trx_commit = 2

Attachment: binlog_off_trx_2.LOG (text/plain), 92.50 KiB.

[26 Oct 2007 12:13] Kristian Koehntopp
FileMon log of DB/2 doing the very same benchmark

Attachment: db2_prozesse_only.LOG (text/plain), 187.89 KiB.

[26 Oct 2007 12:14] Kristian Koehntopp
innodb_flush_method = normal/unbuffered differences

Attachment: create_file_calls.txt (text/plain), 1.30 KiB.