On 8/23/06, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
> On 8/21/06, Kenneth Porter <shiva@sewingwitch.com> wrote:
>
> > > Scalability and performance: Limited due to file binary diff
> > > versioning process.
> >
> > Unknown. [Seeking developer input.]
> >
>
> Ironically, whenever I've talked to Perforce users their big complaint
> seems to be scalability, p4 really falls down with many clients that
> have large working copies, due to the amount of state it needs to keep
> in memory on the server.
>
> As for binary diffing being a performance problem for svn, I think
> they're kind of stretching there...
I evaluated Perforce, having used in the past both StarTeam and now
Subversion. I found Perforce to be very similar to StarTeam in terms
of its heavy use of the network connection and complex GUI client.
LIke StarTeam it requires you to first "Edit" or "Checkout" the file.
It keeps two different revisions (?) with a file, the depot revision
and the changeset revision perhaps. It is very confusing. I am used
to working with StarTeam and now Subversion.
Sean
>
> -garrett
>
> ---------------------------------------------------------------------
> 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 Thu Aug 24 22:33:22 2006