Replication and Binary Logging Options and Variables delay to increase contention and therefore reduce throughput. Typically, the benefits of setting a delay outweigh the drawbacks, but tuning should always be carried out to determine the optimal setting. • binlog_group_commit_sync_no_delay_count • binlog_max_flush_queue_time • binlog_order_commits binlog_max_flush_queue_time  is deprecated, and is marked for eventual removal in a future MySQL release. Formerly, this system variable controlled the time in microseconds to continue reading transactions from the flush queue before proceeding with group commit. It no longer has any effect. The maximum number of transactions to wait for before aborting the current delay as specified by binlog_group_commit_sync_delay . If  binlog_group_commit_sync_delay  is set to 0, then this option has no effect. 3553 Command-Line Format --binlog-group-commit-sync-no-delay- count=# System Variable binlog_group_commit_sync_no_delay_count Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Integer Default Value 0 Minimum Value 0 Maximum Value 100000 Command-Line Format --binlog-max-flush-queue-time=# Deprecated Yes System Variable binlog_max_flush_queue_time Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Integer Default Value 0 Minimum Value 0 Maximum Value 100000 Command-Line Format --binlog-order-commits[={OFF|ON}] System Variable binlog_order_commits Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Boolean Default Value ON