3 ms·
Regarding #2, we do normally run MySQL with full transactional durability at Facebook. We have for a very long time (several years at least). For example, her
by HarrisonFisk 14y ago
Regarding #2, we do normally run MySQL with full transactional durability at Facebook. We have for a very long time (several years at least). For example, here is a FB note regarding our enhancing performance under full durability in MySQL from Oct 2010:
https://www.facebook.com/note.php?note_id=438641125932 https://www.facebook.com/note.php?note_id=438641125932
- nikita 14y agoHarrison, what are these settings for InnoDB? innodb_flush_log_at_trx_commit, innodb_flush_methodm, innodb_doublewrite,
- midom 14y ago1, O_DIRECT, 1
- HarrisonFisk 14y agoThe primary settings are: sync_binlog=1 innodb_flush_log_at_trx_commit=1 (which is default, but we add it to our configs since we run with =2 on the slaves since they don't need full durability) We do use some performance related settings related to this as well: innodb_flush_method = O_DIRECT innodb_prepare_commit_mutex=0 (enables group commit in the Facebook patch, other branches have a different setting) For settings like innodb_doublewrite we leave the default of enabled.