A recent change to the transaction ID allocation code introduced a performance bottleneck and none of our automated performance tests noticed it. The change that introduced the performance regression was
The bottleneck was created when releasing a transaction ID, and the place that really notices that is an in cache update heavy workload.
I ran the following workload:
We should add that test case to Jenkins, so we detect similar performance regressions in the future.