On Fri, Jul 7, 2017 at 8:54 AM, Jacek Materna <ja...@assembla.com> wrote: > Paul, > > Got back from Ops. We don't have anything "special" setup other than what > already been mentioned. Overall the defining metrics for commit performance > are: ssh vs https, rtt on the network path and "randomness" of the blobs > going up. > > No magic params on our end. We have it tuned the max via the metrics above. > > Most of the real world use cases require the default settings so curl, etc > isn't seen a lot in the wild. > > Overall Dav and http is a poor transport in general for SVN. > > Hope it helps. > > -- > Jacek Materna
It would be interesting to know whether the remaining 1:10 factor is caused by the transport or by the back-end (with its server-side deltification and FSFS transaction features). I don't know if it would be possible for Paul to test the same setup with svn+ssh. OTOH, that would probably not be a very good comparison, because with svn+ssh you can't use SVNAutoVersioning and curl, you'd have to use a normal svn client, so IIUC it's not possible to eliminate the client-side deltification. Unless Philip or someone else knows another trick for that :). -- Johan
