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

Re: performance enhancement by working copy svn server

From: Listman <listman_at_burble.net>
Date: Sat, 17 May 2008 15:35:26 -0700

On May 17, 2008, at 2:28 PM- May 17, 2008, Steinar Bang wrote:

>>>>>> Listman <listman_at_burble.net>:
>> Agreed, this is one of the advantages of Perforce, the meta-data is
>> saved on the server not in the WC and there's no chance of a
>> misbehaving tool breaking the working copy..
> Storing the WC on the server, is a behaviour of Perforce I would not
> like subversion to replicate. It causes problems with scaling on the
> server, and limits/complicates offline operations.
> (not that I think that storing the WC on the server is the plan. The
> way I've read the discussions on the list, the "single file or subdir"
> mentioned above, will be on the client machine)

Subversion's working copy gets broken regularly in our environment and
other companies I've worked. Scattering it across the filesystem is a
recipe for disaster in my experience.

The reality is that 90% of companies will put their user accounts (and
hence the Subversion meta-data) on a fileserver. Its seldom that
the .svn directories actually local to the client machine.

This idea of "offline operations" maybe useful in small, open-source
type activities, but isn't the reality in most corporations.

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-18 00:35:52 CEST

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.