You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Straw, Scott J" <Sc...@UNISYS.com> on 2006/07/06 16:56:45 UTC
svn log hangs?
"svn log <fileName>" is hung or taking over an hour to run. We are
using Apache on the respository server, and clients are using Subversion
1.2.3.
Any ideas?
- Scott
________________________________________________________________________
____________
Scott J. Straw
Unisys Corporation, Roseville, MN
(651) 635-6618
Scott.Straw@Unisys.Com
________________________________________________________________________
____________
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.
________________________________________________________________________
____________
RE: svn log hangs?
Posted by "Straw, Scott J" <Sc...@UNISYS.com>.
Thanks, everyone!
Disabling SVNPathAuthz did the trick.
Matt, I'll try the mod_deflate setting, too. Thanks!
- Scott
________________________________
From: Matt Doran [mailto:matt.doran@papercut.biz]
Sent: Friday, July 07, 2006 7:59 PM
To: Straw, Scott J
Cc: users@subversion.tigris.org
Subject: Re: svn log hangs?
Straw, Scott J wrote:
"svn log <fileName>" is hung or taking over an hour to run. We are
using Apache on the respository server, and clients are using Subversion
1.2.3.
Any ideas?
The most common cause of log slowness when using HTTP is SVNPathAuthz.
Disabling this dramatically increases log performance. You can read
about it here.
http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.s
erverconfig.httpd.authz.pathauthzoff
My understanding is that disabling this does not disable security
completely, but disables the checking of "sub-paths" for the request.
For example, when this is enabled and you do a "log", it checks that
every path in that commit is accessible by the user, so that there is no
information leak about parts of the repository you don't have access to.
But I think for most people this is overkill. Authz will still
restrict read/write access to the paths you've defined. If you
disable this option, then users can see that something has changed in a
path that they might not have read access to .... but they still can't
view the contents of the path.
If running svn log (and many other operations) over a slower connection,
I've found that enabling mod_deflate to compress the data over the wire
also makes things much faster.
http://httpd.apache.org/docs/2.0/mod/mod_deflate.html
Cheers,
Matt
Re: svn log hangs?
Posted by Matt Doran <ma...@papercut.biz>.
Straw, Scott J wrote:
>
> "svn log <fileName>" is hung or taking over an hour to run. We are
> using Apache on the respository server, and clients are using
> Subversion 1.2.3.
>
>
>
> Any ideas?
>
>
>
The most common cause of log slowness when using HTTP is SVNPathAuthz.
Disabling this dramatically increases log performance. You can read
about it here.
http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serverconfig.httpd.authz.pathauthzoff
My understanding is that disabling this does not disable security
completely, but disables the checking of "sub-paths" for the request.
For example, when this is enabled and you do a "log", it checks that
every path in that commit is accessible by the user, so that there is no
information leak about parts of the repository you don't have access
to. But I think for most people this is overkill. Authz will still
restrict read/write access to the paths you've defined. If you
disable this option, then users can see that something has changed in a
path that they might not have read access to .... but they still can't
view the contents of the path.
If running svn log (and many other operations) over a slower connection,
I've found that enabling mod_deflate to compress the data over the wire
also makes things much faster.
http://httpd.apache.org/docs/2.0/mod/mod_deflate.html
Cheers,
Matt
Re: svn log hangs?
Posted by Bernhard Merkle <ne...@merkleonline.de>.
same problem here. I have converted a large CVS repo to SVN with cvs2svn
and now the client nearly feezes when i invoke log/history in
TortoiseSVN (SVN and TSVN all new releases and server is run both with
svn:// and http://)
any idea how to resolve this problem ?
kind regards,
Bernhard.
Stephen Davis wrote:
> I have seen 18 minute logs using Apache and FSFS for a single file with
> somewhere on the order of 4500 revisions. How many revisions does this
> file have?
>
> Speaking of which, I know Subversion is doing a lot of work for such
> files but perhaps someone on the dev team could look at the performance
> of the log operation a little more? I get a lot of flack at work from
> some CVS old-timers about this issue. :-)
>
> BTW, if you don't need all of the log and you can upgrade to 1.3.x, the
> "--limit=N" option to svn log is a lifesaver.
>
> stephen
>
> On Jul 6, 2006, at 9:56 AM, Straw, Scott J wrote:
>
>> “svn log <fileName>” is hung or taking over an hour to run. We are
>> using Apache on the respository server, and clients are using
>> Subversion 1.2.3.
>>
>>
>>
>> Any ideas?
>>
>>
>>
>> - Scott
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn log hangs?
Posted by Stephen Davis <su...@soundgeek.org>.
I have seen 18 minute logs using Apache and FSFS for a single file
with somewhere on the order of 4500 revisions. How many revisions
does this file have?
Speaking of which, I know Subversion is doing a lot of work for such
files but perhaps someone on the dev team could look at the
performance of the log operation a little more? I get a lot of flack
at work from some CVS old-timers about this issue. :-)
BTW, if you don't need all of the log and you can upgrade to 1.3.x,
the "--limit=N" option to svn log is a lifesaver.
stephen
On Jul 6, 2006, at 9:56 AM, Straw, Scott J wrote:
> “svn log <fileName>” is hung or taking over an hour to run. We are
> using Apache on the respository server, and clients are using
> Subversion 1.2.3.
>
>
>
> Any ideas?
>
>
>
> - Scott