[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Performance

From: Christopher Ness <chris_at_nesser.org>
Date: 2005-09-12 23:17:27 CEST

On Mon, 2005-09-12 at 15:39 -0500, Ben Collins-Sussman wrote:
> On Sep 12, 2005, at 3:24 PM, William Nagel wrote:
>
> >
> > This is a fairly well-known issue. Because of design difference
> > between Subversion and CVS, checkouts can take significantly longer
> > under Subversion. Just about everything else runs faster though,
> > so it's a tradeoff that most people consider acceptable (given that
> > you're not normally going to check out a working copy very often).
> >
> >
>
> A checkout taking 4x longer than cvs is not normal.
>
> When we compared CVS vs. SVN checkouts just before svn 1.0 was
> released, we never saw svn behave worse than 2x slower. Usually it
> was more like 1.5x slower. So I think something is fishy in his
> setup...

What method was used? It looks like http:// since you mentioned an
apache revision number.

What kind of authz are you using? Is the repository wide open for
anyone or are there permissions for each dir?

The book says the log sub-command is mostly hit by the overhead of
checking the paths for each directory. If you have that many files, I'm
thinking you have quite a nested directory structure.

This link will show you how to disable authz and explains what is going
on in more detail:
  http://svnbook.red-bean.com/en/1.1/ch06s04.html#svn-ch-6-sect-4.4.3

Of course if you _cannot_ disable authz for your repository because you
need those features, then ...

ALSO: I'd like to know what type of file system you are using (likely
ext3). If you have time, try the repository in a Reiser file system
partition and post your benchmark times again.

Cheers,
Chris

-- 
PGP Public Key: http://www.nesser.org/pgp-key/
17:10:02 up 10 min, 2 users, load average: 0.03, 0.29, 0.23

Received on Mon Sep 12 23:30:15 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.