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

Re: Improving the performance of libsvn_wc for checkouts/updates/switches

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2004-05-23 01:51:12 CEST

Josh Pieper <jjp@pobox.com> writes:

> This sounds workable. Would it be acceptable to use just a postfixed
> number (log.1, log.2, etc...), and store the last used one in the
> adm_access baton? When it comes time to run them, just loop from 1 to
> the last used, then reset the last used. Sorting would be O(n log n),
> which while not bad, isn't strictly necessary since we have a lock on
> the directory.

Naming them log.1, log.2, etc. and then running them in that order and
stopping when at the first not-found file will probably do. Don't
rely on anything stored in the access baton since that won't work when
running "svn cleanup".

The file handling needs to be considered carefully--it's important to
make sure that the lock is never removed while leaving a log.N file
behind, since it could inadvertantly become live if an update creates
log files up to log.N-1.

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 23 01:51:26 2004

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

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