RE: performance enhancement by working copy svn server

> libsvn_wc rewrite which
> (1) centralizes metadata in one place and
> (2) allows users the option of 'svn edit' to tell svn what you're
> changing, so that 'svn status/update/commit' no longer need
> to traverse the tree.

With the wc rewrite, are you talking about somehow preventing extraneous processes, such as "vi somefile" from accessing files in a WC "behind the back" of the svn client? Or just telling users, "don't do that" and assuming during the stat/up/commit that they've behaved properly?

The ideal, which may be very difficult to achieve, is the ability to monitor FS access, to automatically "notice" a file changed on the fly. This extra FS overhead is analogous to journaling, where you spread out the fsck overhead during normal operation, instead of letting it all pile up into one big operation.

This e-mail message may contain proprietary, confidential or legally privileged information for the sole use of the person or entity to whom this message was originally addressed. Any review, e-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this e-mail in error kindly delete this e-mail from your records. If it appears that this mail has been forwarded to you without proper authority, please notify us immediately at netadmin_at_patni.com and delete this mail.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-10 17:02:14 CEST