I just want to note, that on your screenshot unpatched version runs 400K tps, while patched runs 280K tps. I see the dates are different and this effect is not observed in [0]. Probably, you run tests on different machines.
While your experiments clearly shows that patch can save DB from degradation under pathological workload it would be great to ensure patch does not incur penalty on normal workload.
Makes sense. I'll try to find time to make a direct comparison.
I documented all the steps in detail in the GitLab issue, so anyone interested can reproduce it and explore the problem at different angles.
