Allow setting change of innodb_flush_log_at_trx_commit
Per Microsoft's post here: https://docs.microsoft.com/en-us/azure/virtual-machines/linux/classic/optimize-mysql, please consider adding some of the server parameters suggested in the post as configurable options. In particular, innodb_flush_log_at_trx_commit, to improve performance and varying workloads.
Any movement on this? We are noticing that Azure is a tad more performant, but it still requires an average of $300/month just to get decent performance out of running a Drupal setup.
Pavel Sher commented
+1 for allowing this. Seems it's up to developer to decide whether this data loss is ok or not. In some systems it's fine to flush transaction log a bit later as data loss is not critical and performance is more important. And with value set to 0 or 2 insert operations work significantly faster.
BTW Amazon RDS allows to change it.
Hong Wang commented
We have no plan to let user the innodb_flush_log_at_trx_commit. Setting the value to 0 or 2 will potential have unrecoverable data loss.