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

Re: Re: Arguments to favor Subversion against Perforce

From: David Waite <dwaite_at_gmail.com>
Date: 2004-11-24 03:06:12 CET

Perforce stores all state on the server. Because of this, locking is
required (so that the server has a way to verify state without you
sending md5's of every file back up to it on operations). A server on
another network just feels dog slow because you have to perform so
many round trips to the perforce server to do 'real work', and your
tool is just blocked until it returns.

Perforce is fast if the machine is powerful and on the local (_wired_)
lan. Anything else and it just is dog slow.

Or I used to say 'its a bad idea to buy a product that has an
architecture which was dictated by a licensing model'.

-David Waite

On Tue, 23 Nov 2004 17:33:38 -0800, Krebs, Steven
<steven.krebs@intel.com> wrote:
> BSE writes:
> >I'm wondering whether someone did a speed/performance comparison
> between
> >Subversion and Perforce in a multi-site environment, i.e. throughput or
> >delay figures for distributed users.
>
> I don't have official data, but Perforce was one of the faster tools, I
> think the speed of both Subversion and Perforce is sufficient for a
> multi-site distributed development team. (Our team is spread across
> Washington (state), Oregon, California, and India).
>
>
>
> Steve
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 24 03:08:39 2004

This is an archived mail posted to the Subversion Users mailing list.