The size in bytes of the buffer that innodb uses to write to the log files on disk. So the case that you are describing will not occur as transactions. The following code will limit the scope of a transaction to a specific number of records in order to reduce the size of the transaction.
At The Moment Maxtxsize = 16384 Bytes (Including Metadata).
This is more than enough, to describe transaction's body and add a reach metadata to it. I made the assumption that there is a limit to the amount of work a transaction can perform before it runs out of alloted space for virtual tables to hold data until it is cleared to commit. To optimize and minimize the amount of data written to the log, please refer to the transactions best practices article.
It Is Not Applied Across All Concurrent Transactions.
November 23, 2010 at 1:17 pm #388291. Transactions larger than this size are rolled back by the receiving member and are not broadcast to the group. This is a strength of the etherem network, it does scale.
The Transaction Size Limit Is Applied Per Transaction Or Operation.
0.01 btc fee per kilobyte of transaction, but: Below are the steps to limit transaction log files. Transaction size limit (2147483647) exceeded:
Use The System Variable Group_Replication_Transaction_Size_Limit To Specify The Maximum Transaction Size That The Group Accepts.
This configuration item may be used to specify the max. The transaction size limit, at the time of writing, is about 780kb (about 3 million gas). But the state and contract jar is easily over 20 mb for even the simplest use case.