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

Re: Speeding up the 'svn commit' process?

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2002-07-10 18:14:21 CEST

Justin Erenkrantz <jerenkrantz@apache.org> writes:

> On Wed, Jul 10, 2002 at 11:46:18AM +0100, Philip Martin wrote:
> > I've started looking at issue #749
> >
> > http://subversion.tigris.org/issues/show_bug.cgi?id=749
> >
> > This will allow some cacheing of the entries.
> Hey, whaddaya know. =)
> So, just to make sure we're on the same wavelength, when we
> create this baton, we should be performing svn_wc_entries_read()
> and storing a copy of that in the baton. Perhaps going through
> and creating a duplicate hashtable that has the deleted items
> removed - still no need for a reparse of the entries file.
> Then, any function that accesses the wc (say svn_wc_entry,
> svn_wc_props_modified_p, etc, will require this baton). They
> can then use baton->entries to get their entry.
> Am I close? -- justin

Yes. Initially there will simply be a requirement to pass a baton
into those functions that modify the adminstrative area, thus ensuring
that all modifications are using the log file mechanism. I'm working
on introducing the baton without altering very much else, only making
changes that are necessary to get the correct locking/loggy behaviour.
Once the locking works, adding cacheing to the baton should be

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 10 18:14:48 2002

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.