The InnoDB rollback segment could be a bottleneck on high-capacity systems, because it can handle a maximum of 1023 concurrent transactions that change any data. (Read-only transactions do not count against that maximum.) Starting in InnoDB storage engine 1.1, the limit on concurrent transactions is greatly expanded. The single rollback segment is divided into 131,072 (128K) segments, each of which can support up to 1023 transactions that perform writes. Each transaction is assigned to one of the rollback segments using a hashing function, and remains tied to that rollback segment for the duration. This enhancement improves both scalability (higher number of concurrent transactions) and performance (less contention when different threads access the rollback segments).

To take advantage of this feature, you do not need to create any new database or tables, or reconfigure anything. You must do a slow shutdown before upgrading to the InnoDB storage engine 1.1, or some time afterward. InnoDB makes the required changes inside the system tablespace automatically, the first time you restart after performing a slow shutdown.