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

RE: svn up take a very long time using trunk revision 37502

From: Marc Haesen <marc.haesen_at_oneaccess-net.com>
Date: Mon, 4 May 2009 07:53:21 +0200

In indeed first had to convert the wc by the svn cleanup command. The svn cleanup command itself was not extremely slow.
The svn up is slow even if no new files need to be pulled down from the server.
With the old client, the svn up command took a few minutes (depending on which files are already in the disk cache)


-----Original Message-----
From: Mark Phippard [mailto:markphip_at_gmail.com]
Sent: 30 April 2009 14:39
To: Hyrum K. Wright
Cc: Marc Haesen; dev_at_subversion.tigris.org
Subject: Re: svn up take a very long time using trunk revision 37502

On Thu, Apr 30, 2009 at 8:16 AM, Hyrum K. Wright <hyrum_at_hyrumwright.org> wrote:
> On Apr 30, 2009, at 2:29 AM, Marc Haesen wrote:
>> I am currently using subversion revision 37502 from trunk on windows
>> (checkout of yesterday).
>> I have a working copy of https://docbook.svn.sourceforge.net/svnroot/docbook/trunk
>> When I do the 'svn up' command on this working copy it takes hours.
>> In the debugger I see that it keeps on executing the tweak_entries
>> routine. In filemon I see that it is continuously writing to the
>> wc.db files and continuously creating wc.db-journal files. In the
>> task manager I see that it is writing giga bytes of data to disk.
>> Finally the svn up finishes successfully.
> Subversion trunk now has the new wc-ng storage format for working copy
> access.  It is known to be slow, and performance will improve
> significantly as we progress toward 1.7.  That is part of the
> excitement of running Subversion trunk!
> Glad to hear that your update finishes successfully, though. :)

Before we just dismiss this as something that gets faster it seems
like a few questions are in order. Presumably Marc had to run svn
cleanup to upgrade the WC to the new format first, right? So the
slowness was not in converting the working copy. How big was this
update? Did it pull down a lot of new content? How long were the
updates taking with the old WC?

The wc.db should not be writing gigabytes of data to disk. That would
be a pretty large WC. If the update pulled down gigabytes worth of
new file content, then sure it probably should take hours. I'd like
to hear a little more about what Marc was expecting here.

Mark Phippard
Received on 2009-05-04 07:53:43 CEST

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