You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by ListMan <li...@burble.net> on 2006/05/06 03:06:22 UTC

comparison times with perforce

hi, anyone have any comparison times with perforce? i'm concerned  
about commit times on large binary data.. anyone done the comparison?


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: comparison times with perforce

Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On 5/5/06, ListMan <li...@burble.net> wrote:
>
> hi, anyone have any comparison times with perforce? i'm concerned
> about commit times on large binary data.. anyone done the comparison?

I know there have been comparisons done in the past, but I don't know
where any of them are off the top of my head.

In short though, if you're on a local network Perforce will likely be
faster for many operations, because it stores lots of state server
side and thus doesn't need to crawl the working copy to figure out
what has changed.  That said, its lack of client side pristine copies
of files means it can't easily send diffs to the server when
committing, which could slow it down.  It'll also probably perform
worse over a WAN due to the fact that it needs to talk to the server
for just about anything you want to do.

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org