On Mon, Apr 28, 2014 at 10:23 AM, Branko Čibej <brane_at_wandisco.com> wrote:
>
> "Mostly read-only" would be a pretty good description of mature
> project maintenance - which in my experience is where most developer
> time goes.
>
>
> You're confusing the contents of versioned files with working copy metadata.
> The latter is never mostly read-only; even a simple "svn update" that
> doesn't change any working file can modify lots of metadata, and this is
> where locking is involved.
>
> Will the subversion performance issue affect local storage that is
> exported via nfs or just the clients mounting it remotely?
>
>
> It's not a Subversion performance issue, it's an NFS performance and
> correctness issue; let's not confuse issues here. :)
Call it what you will - I just want to be realistic about what to
expect from application performance in common environments.
> That said, simultaneous local and (NFS) remote access to the same working
> copy is an extremely bad idea; it makes triggering the NFS atomicity bug far
> more likely.
There's no concurrent access happening - just home directories where a
user will be working on one machine or another - which is mostly
transparent to normal applications.. Should there be a difference if
they work on the server hosting the exported partition or will it
still be slow due to locking?
--
Les Mikesell
lesmikesell_at_gmail.com
Received on 2014-04-28 17:41:39 CEST