On Wed, Jun 30, 2010 at 12:01 PM, Edward Ned Harvey wrote:
> Actually, I'm surprised what I'm learning now. Although it matters if the
> server is busy, that's not the root cause of the problem. Also, changing
> the compression level makes a difference, but it's not the difference we
> were hop
[ can you please reply as text, not HTML? thanks. ]
Edward Ned Harvey wrote on Wed, 30 Jun 2010 at 19:01 -:
> . If I export all the different rev's of that file (parent dir, no
> subdirs) then some rev's are repeatably less than 11sec to export, while
> other revs are repeatably 15min.
> From: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
>
> > I've had the greatest complaints for >15min commits.
> >
>
> So, a commit takes 1min when the server is idle, and 15min when the
> server is busy.
Actually, I'm surprised what I'm learning now. Although it matters if the
serv
(fixed quoting)
Edward Ned Harvey wrote on Tue, 29 Jun 2010 at 23:57 -:
> Daniel Shahaf [mailto:d...@daniel.shahaf.name]
> > Edward Ned Harvey wrote on Tue, 29 Jun 2010 at 07:15 -:
> > > Some people are seeing 20min commit times on changes they could have
> > > copied uncompressed in 1min.
> From: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
>
> Edward Ned Harvey wrote on Tue, 29 Jun 2010 at 07:15 -:
> > Svnserve is using standard zlib (not a parallel implementation) so
>
> You can disable all (most?) compression by not advertising the
> svndiff1 capability in svnserve/serve.
Edward Ned Harvey wrote on Tue, 29 Jun 2010 at 07:15 -:
> Svnserve is using standard zlib (not a parallel implementation) so
You can disable all (most?) compression by not advertising the
svndiff1 capability in svnserve/serve.c.
> Some people are seeing 20min commit times on changes they coul
6 matches
Mail list logo
