Bert Huijben wrote:
> I suggested implementing this fix for 1.6 as the actual implementation of a
> stable fix is only a few hours of work (I could have completed this a few
> days ago).
> The sentiment on the development list (and irc) was however that the actual
> fix should wait for 1.7. (Reasoning: Not needed for 1.7 and the performance
> is not worse than that of 1.0-1.5.. and that this should be checked
> thoroughly of course).
> (See the dev_at_s.t.o archive:
> 4340 and follow ups)
I think it's really unfortunate that this will not get implemented for
1.6. I kind of understand the developers not wanting to make a big
change right before release, or else we'd end up with the types of
problems we've had with svn-merge property.
On the other hand, all this locking/unlocking really slows down large
workspaces. Is there anything we can do on the client side to overcome
Is there a reason this is only a problem on windows and not *nix?
Perhaps something can still be done to make things a bit faster. For
example, I think Tortoise and Subclipse use a different order for
creating/removing lock files. Perhaps that speed things up a bit? What
about block size on the filesystem - does that have any effect?
Maybe there is a way to defrag the filesystem such that the creation of
these files takes less time? Put all folders together or something?
Just throwing things out there.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-13 19:33:08 CET