I’m afriad not (unless I’ve missiagnosed that particular problem).
Probably the only way to account for @tutschku’s issue here is to do runs with his whole patch on data sets of a comprable size, using a build with debug info so that once performance has started to degrade we can attach a debugger and actually see what’s happening. When I last looked at this, here, I wasn’t able to reproduce on a smaller set of data, which I why I think we’ll need to go all in.