14 messages in com.perforce.perforce-user[p4] Remote Depots
FromSent OnAttachments
case...@autodesk.com26 Feb 2002 13:58 
Dave Lewis26 Feb 2002 14:29 
Stephen Vance26 Feb 2002 14:35 
Steve Smythe26 Feb 2002 15:16 
Eivind Hagen26 Feb 2002 15:43 
Kaelin Colclasure26 Feb 2002 18:35 
Paul Goffin27 Feb 2002 01:03 
Arnt Gulbrandsen27 Feb 2002 01:43 
Paul Goffin27 Feb 2002 02:41 
Arnt Gulbrandsen27 Feb 2002 03:08 
joha...@esrange.ssc.se27 Feb 2002 04:11 
Paul Goffin27 Feb 2002 05:06 
Kaelin Colclasure27 Feb 2002 09:13 
Dave Lewis27 Feb 2002 10:12 
Subject:[p4] Remote Depots
From:Stephen Vance (ste@vance.com)
Date:02/26/2002 02:35:18 PM
List:com.perforce.perforce-user

I have done very little with remote depots.

That said, my understanding is that there is some local caching with remote depots that may speed up the local access.

Can anyone on the list confirm or deny?

Steve

At 01:58 PM 2/26/2002 -0800, casey.motherway at autodesk.com wrote:

Does one of these scenarios have a performance advantage over the other:

[1] Main source code repository is set up in Portland Oregon on server SCM1_OR. Developers in San Francisco have there Perforce clients pointing at SCM1_OR.

[2] Main source code repository is set up in Portland, Oregon on server SCM1_OR. A second Perforce server is set up for SF developers on SCM2_SF and a remote depot is created which maps to sources on SCM1_OR.

Is there any difference in speed if a SF developer synced 20,000 source files directly from SCM1_OR or used the remote depot on SCM2_SF.

The only thing I'm interested in is performance (particularly when syncing to very large numbers of files to a clean workspace). I'm not worried about read only permissions or anything else. From reading Admin docs online, I get the impression that the remote depot is not any faster, that both scenarios are pretty much the same. The remote depot in SF just provides a convenient link to the Oregon depot. Someone please enlighten me as to what goes on behind the scenes of remote depots.

Thank,