eliminating sequential bottlenecks for huge commit and merge ops

As Daniel mentioned to me on irc, subversion doesn't use threading
internally, so things like client side commit processing and merge
operations are done one file at at time IIUC.

Over in the openoffice podling we have a use-case for a 9GB working copy
that regularly sees churn on each file in the tree.  commit and merge
operations for such changes take upwards of 20min, and I'm wondering
if there's anything we could do here to reduce that processing time
by 2x or better by threading the per-dir processing somehow.

Thoughts?
Received on 2012-01-04 19:34:19 CET