i've seen the deletes dominating commit time quite often, so obviously it would be very useful to be able to absorb this optimization sooner than later (whats the timeframe for 3.1?)
I'm not sure how much gain you can expect from this patch (there are
many factors involved) – maybe try it & report back?
Not sure what the timeframe is for 3.1 at this point...
otherwise i'll have to override the classes involved and pull in this patch (never like this approach myself)
I understand... you could run with trunk (and report back!)
It doesn't break backwards compatibility and it's well under the hood so it seems like something that go into a sub decimal release?
I know it's tempting to do so, but I think it's important to hold the
line on only back-porting important bug fixes... as innocent as this
change looks, it's always possible I screwed something up, and so
why risk a point release with that? Point releases are supposed to
be as stable as we can possibly make them.
This way the change has plenty of time to "bake" on trunk and if
something is amiss we'll have much more time/attention to catch it.
I'd rather see us release a 3.1 sooner rather than later, instead.