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

Philip Martin wrote:
> 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".

Yeah, I was actually just going to use that as an optimization when
writing, and the dir_baton makes more sense now that I think about it.

> 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.

So, how about we execute all the log files in order, then erase them
in reverse order? That should take care of any unforseen crashes,
yes?

---------------------------------------------------------------------
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:56:00 2004