> -----Original Message-----
> From: Greg Stein [mailto:gstein_at_gmail.com]
> Sent: vrijdag 4 mei 2012 21:15
> To: Moe, Mark
> Cc: Philip Martin; dev_at_subversion.apache.org; Braun, Eric
> Subject: Re: svn ci performance issue with 1.7.x and nfs mounted working
> copies
>
> Well... your interest has already been noted :-) Maybe you're asking
> how you can help get the bug fixed? Volunteering, of course (as we all
> are).
>
> Philip noted a couple problems in the bug report. Focusing on how to
> resolve those is likely the start of the work. I imagine at least two
> approaches: ensure the same underlying wc_db instance is used in both
> cases, or that we have a way to open non-exclusive in limited cases.
>
> For example, with the latter approach: maybe when client context is
> created, it can use the default exclusive case, and certain clients
> can specify non-exclusive access (as a GUI may choose to do). Of
> course, then we get into problems with that one client that defaults
> to exclusive and tries to manipulate a working copy being
> non-exclusively accessed by that GUI. ... etc :-)
>
> If you're not talking about digging into the code yourself, then... I
> dunno. Maybe one of the Subversion vendors is willing to do spot fixes
> for a fee? Outside of that, it is tough to know when somebody will
> want to dig into the problem :-/
I rewrote some parts of the commit processing on trunk last week, which
should have a positive effect on the use cases reported in this thread.
Is it possible for somebody to see what the performance difference on NFS
is?
I'm using Windows for most of my development and testing, so I can't measure
the impact on NFS. I do see a huge improvement on Windows: The commit
harvesting time is now in the same region as the svn status time for me.
Bert
Received on 2012-05-14 11:02:56 CEST