subversion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Hammant <p...@hammant.org>
Subject Re: Expected speed of commit over HTTP?
Date Thu, 06 Jul 2017 12:31:31 GMT
Jacek, Can you share any config settings for mod_dav that might be areas to
experiment with ?

And, yes, just because the file commit has no discernible deltas at all,
doesn't mean that Svn doesn't attempt to make its own determination.  I
wasn't using .bin suffixes as it happens but I'll bet there's something in
amongst mimetypes and suffixes somewhere that allows skipping.

-ph

On Thu, Jul 6, 2017 at 8:07 AM, Jacek Materna <jacek@assembla.com> wrote:

> We've say 2-3x speed decrease using HTTP vs SSH in our cloud. With SSH and
> some tuning we are getting close to the IO rate on the end server of any
> size. HTTP/mod_dav and RTT is usually the culprit in our cases, on a LAN
> that issues collapses. Likely server side processing of the delta's?
>
> -jacek
>
> On Thu, Jul 6, 2017 at 1:54 PM, Paul Hammant <paul@hammant.org> wrote:
>
>> For something that's 500MB in size (random binary data) I'm experiencing
>> commits taking
>> 10x longer than a straight copy to the drive the Svn repo is on.
>>
>> Both timings are on the same Ubuntu 17.04 machine, with the boot drive
>> being the starting position of the 512MB file and a USB3 mounted 4TB
>> seagate hard drive being the destination.
>>
>> My goal is to fill the 4TB drive with commits for the simple experience
>> of that.
>>
>> How many places in the Apache2 --> mod_dav --> mod_dav_svn handoff does
>> the 512MB temporarily manifest itself in a file system on the way to its
>> ultimate destination?  Is 1/10th speed the expectation?  Sure, I get that
>> 7bit/8bit shenanigans are a factor, but not that much right?
>>
>> - Paul
>>
>>
>
>
> --
>
> Jacek Materna
> CTO
>
> Assembla
> +1 210 410 7661 <(210)%20410-7661>
> +48 578 296 708 <+48%20578%20296%20708>
>

Mime
View raw message