Binlog commit_wait count
The configuration variables for artificial delay are binlog-group-commit-sync-delay delay in microseconds and binlog-group-commit-sync-no-delay-count number of transactions to wait for before deciding to abort waiting. Hi, Morgan, I have a question: I even remember a post about group commit being fixed for InnoDB, binlog commit_wait count was true when you used InnoDB without replication. Each time it returns to point A to pick up new passengers, it will collect everyone who is waiting and transfer them across binlog commit_wait count point B.
And most of the threads use it when they are waiting for their leader to finish BGC process. I have binlog commit_wait count answer binlog commit_wait count from the Developer on this: What defaults would you like to see changed in MySQL 5. In BGC, there are leader thread and non-leader thread. I would have preferred back in the day for this to be called out in the upstream docs as a serious performance problem.
Second, both of binlog commit_wait count and non-leader threads just hold the lock a very little time. When the ferry arrives back at point A to pick up binlog commit_wait count passengers, it can be configured to wait just a little bit longer with the knowledge that new passengers will likely arrive. In BGC, there are leader thread and non-leader thread.
This is measurably better performance in real-life situations where many passengers tend to arrive while waiting for binlog commit_wait count ferry to arrive back at point A, and the trip between A and B tends to take some time. Leader threads need to wakeup all other thread in binlog commit_wait count queue after finishing the BGC process. This may save you on roundtrips and improve the overall number of passengers that can be transported. It works by default.
I have an answer back from the Developer on this: Hi, Morgan, I binlog commit_wait count a question: You can say it is hot, since very thread needs to use it. I even remember a post about group commit being fixed for InnoDB, which binlog commit_wait count true when you used InnoDB without replication. In this example passengers are obviously transactions, and the ferry is an expensive fsync operation.