Difference between revisions of "Performance tuning"

Jump to navigation Jump to search
316 bytes added ,  19:04, 28 May 2018
Add advice based on ZoL #2872 and #7573
(Copy a warning from the source about skip-innodb_doublewrite, which may not be safe. →‎Database workloads)
(Add advice based on ZoL #2872 and #7573)
Line 168: Line 168:


Set skip-innodb_doublewrite in my.cnf to prevent innodb from also writing twice. The double writes are a data integrity feature meant to protect against partially-written pages, but those are not possible on ZFS.[https://www.percona.com/blog/2014/05/23/improve-innodb-performance-write-bound-loads/] WARNING: The source now says, "Update: do not do this, this has been proven to corrupt data!"
Set skip-innodb_doublewrite in my.cnf to prevent innodb from also writing twice. The double writes are a data integrity feature meant to protect against partially-written pages, but those are not possible on ZFS.[https://www.percona.com/blog/2014/05/23/improve-innodb-performance-write-bound-loads/] WARNING: The source now says, "Update: do not do this, this has been proven to corrupt data!"
On Linux, the driver's AIO implementation is a compatibility shim that just barely passes the POSIX standard. InnoDB performance suffers when using its default AIO codepath. Set innodb_use_native_aio=0 and innodb_use_atomic_writes=0 in my.cnf to disable AIO. Both of these settings must be disabled to disable AIO.


====  MyISAM ====
====  MyISAM ====
Editor
348

edits

Navigation menu