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


From: Paul Koning <pkoning_at_equallogic.com>
Date: 2005-09-12 21:21:32 CEST

I'm doing tests of CVS vs. Subversion.

The first test is to checkout a full working directory, on a rather
large repository (35,000 revisions, and the CVS working directory is
foo MB).

In CVS that takes 10 minutes. In Subversion, it takes 46 minutes.
I'm not surprised it takes a little longer, after all SVN has to write
two copies (the regular one and the clean one in .svn). But that
difference is quite surprising.

The other puzzle is that svn sits for a minute or two at the end,
without producing any output and without any significant activity that
I can see. CPU time goes up just a little (17:02 at the end of the
activity, and then 17:04 a little later). The server isn't doing
anything (the httpd thread shows 11:25 CPU time). What's going on

Is it reasonable for things to take this long?

By the way, I changed /dev/random to be /dev/urandom given the earlier
comments about a possible reason for things to get stalled. (Not that
this makes any sense -- what possible use does the server have for
strong random numbers in this process???) So that definitely isn't a
consideration. Actually, I ran the test several times, before and
after that change; the timing was identical.

Subversion 1.2.3, Apache 2.0.54. The machine runs Linux 2.4.21 on a
quad processor Xeon, 1 GB memory.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 12 21:23:43 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.