3 ms·
If I am parsing you right, it sounds like "innodb_log_flush_at_trx_commit = 2" is what you would recommend for a majority of production environments.
by bhauer 13y ago
If I am parsing you right, it sounds like "innodb_log_flush_at_trx_commit = 2" is what you would recommend for a majority of production environments.
- rsynnott 13y agoReally depends on the scenario, but for most web stuff, I'd tend to recommend a setting of 2, if the data durability caveats were acceptable.
- morgo 13y agoDurability will typically be very expensive to implement unless you have a fast SSD or RAID controller with NVRAM, so it will skew the test considerably if you make MySQL offer it, but say MongoDB does not have to. But I do recommend it for the majority of people. Shameless plug: http://www.tocker.ca/2013/06/19/deciding-whether-or-not-to-make-mysql-durable.html http://www.tocker.ca/2013/06/19/deciding-whether-or-not-to-m... Also: http://dom.as/2013/08/09/on-durability/ http://dom.as/2013/08/09/on-durability/ (Domas works on MySQL@Facebook).
- bhauer 13y agoThanks! Just for the record, on our i7 tests, starting with Round 6, we have been using a Samsung 840 Pro SSD for the database server.
- rsynnott 13y agoIncidentally, on the EBS durability thing, it's addressed here: https://forums.aws.amazon.com/thread.jspa?threadID=27590 https://forums.aws.amazon.com/thread.jspa?threadID=27590 - An fsync isn't a guarantee, or wasn't in 2013, but they estimate the risk of loss after fsync to be very low. Can't find anything on whether their newer SSD-providing instances guarantee durability, though.
- morgo 13y agoThat's really cool. Thanks!