drupaladmin
commented
11 months ago We understand that the value of certain MySQL variables is contingent on specific business requirements, so we've decided to remove 'innodb_flush_log_at_trx_commit' from our automated recommendations. However, we've still got you covered! If you wish to adjust this variable, you can easily do so manually via our web interface under the 'Recommended configuration' block settings.
I was just looking through the latest suggestions and saw a recommendation to change the innodb_flush_log_at_trx_commit variable. I think this should definitely include a warning that changing this variable will also change system behaviour. In this case it was actually suggesting a more 'safe' setting, which does seem a bit counterintuitive, considering that it should be suggesting optimizations. I think it would be worse, if it suggested the value 2, where you get less safety, but still strange to have it suggest changing the servers behaviour, without a warning. We have chosen to live with the risk of loosing the last x seconds of transactions on server failures in favour of more optimal disk access, so this setting is actually intended in our case.