You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Bradley Wagner <br...@hannonhill.com> on 2006/11/16 05:28:40 UTC
Cause of SVN Slow Down: https or per-directory access control?
Hey, I recently switched from a repository over http:// with no per
directory access control to one using some complicated per directory
access control and https://. I've noticed that compared to Apache's
SVN repository, for example, mine is very slow even to browse in SVN
Repository Explorer in Eclipse using Subclipse. I'm using the native
libraries on OS X for Subclipse.
Between the switch to secure http (SSL) and per-dir access controls,
which would degrade the performance most? Seems like the per-dir
access control could be pretty slow especially if it has to derive a
path and parse the config file every time. Is svnperms supposed to be
a faster mechanism for doing this?
Bradley
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Cause of SVN Slow Down: https or per-directory access control?
Posted by Erik Huelsmann <eh...@gmail.com>.
On 11/16/06, Bradley Wagner <br...@hannonhill.com> wrote:
> > If you only want to enfore write access, yes.
>
> Not sure I understand. What else would I want to do? I always got the
> sense that svnperms let you do more advanced stuff, but have never
> played around with it.
You could have wanted to control read access. That's not possible with
svnperms...
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Cause of SVN Slow Down: https or per-directory access control?
Posted by Bradley Wagner <br...@hannonhill.com>.
> If you only want to enfore write access, yes.
Not sure I understand. What else would I want to do? I always got the
sense that svnperms let you do more advanced stuff, but have never
played around with it.
Bradley
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Cause of SVN Slow Down: https or per-directory access control?
Posted by Erik Huelsmann <eh...@gmail.com>.
On 11/16/06, Bradley Wagner <br...@hannonhill.com> wrote:
> Hey, I recently switched from a repository over http:// with no per
> directory access control to one using some complicated per directory
> access control and https://. I've noticed that compared to Apache's
> SVN repository, for example, mine is very slow even to browse in SVN
> Repository Explorer in Eclipse using Subclipse. I'm using the native
> libraries on OS X for Subclipse.
>
> Between the switch to secure http (SSL) and per-dir access controls,
> which would degrade the performance most?
Per-directory access control.
> Seems like the per-dir
> access control could be pretty slow especially if it has to derive a
> path and parse the config file every time. Is svnperms supposed to be
> a faster mechanism for doing this?
If you only want to enfore write access, yes.
HTH,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Cause of SVN Slow Down: https or per-directory access control?
Posted by Dmitri Colebatch <di...@colebatch.com>.
I know nothing about the performance of per-directory access control, but I
find it hard to believe that any half-decent hardware these days would incur
any significant performance hit from the ssl for the relatively small
requests that you're describing.
my 2c.
cheers
dim
On 11/16/06, Bradley Wagner <br...@hannonhill.com> wrote:
>
> Hey, I recently switched from a repository over http:// with no per
> directory access control to one using some complicated per directory
> access control and https://. I've noticed that compared to Apache's
> SVN repository, for example, mine is very slow even to browse in SVN
> Repository Explorer in Eclipse using Subclipse. I'm using the native
> libraries on OS X for Subclipse.
>
> Between the switch to secure http (SSL) and per-dir access controls,
> which would degrade the performance most? Seems like the per-dir
> access control could be pretty slow especially if it has to derive a
> path and parse the config file every time. Is svnperms supposed to be
> a faster mechanism for doing this?
>
> Bradley
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>