[p4] Off-site Perforce performance/optimization

Jeff Grills jgrills at drivensnow.org
Thu Nov 2 07:07:04 PST 2006

I have a mail into perforce support about the rsync updated proxy cache
idea.  I'd hope that you could rsync across the primary server's depot files
directly, but those files may be in flux at any point.  It might be
safest/best to have a script which updates a local proxy's cache and then
issues the rsync to push that data out to the offsite proxies, but I guess
you still have to worry when the proxy wants to read a file that's in the
process of being updated by rsync, so it may not be any better.


-----Original Message-----
From: Jeff Desharnais [mailto:jdesharnais at maddocsoftware.com] 
Sent: Thursday, November 02, 2006 9:03 AM
To: karish at well.com; Jeff Grills
Cc: perforce-user at perforce.com
Subject: RE: [p4] Off-site Perforce performance/optimization

We are running P4P with no variables, so it's running in it's default state
(which assumes compression if I understand correctly).

The RSYNC idea is interesting.

Do you think the best way to do it would be to have a proxy setup here for
this project and then use rsync to update the offsite proxy's cache from the
on-site proxy's cache?

Has anyone ever tested this?

-----Original Message-----
From: Chuck Karish [mailto:chuck.karish at gmail.com] 
Sent: Thursday, November 02, 2006 9:53 AM
To: Jeff Grills
Cc: Jeff Desharnais; perforce-user at perforce.com
Subject: Re: [p4] Off-site Perforce performance/optimization

I'll second what Steve Vance said about making sure the server -> proxy
transfers are compressed.

p4p queries the server on every request that doesn't specify a particular
file revision, to find out which version to serve. For small files this can
be slower than transferring the files directly. The minimum size of files to
cache is tunable on 2005.2 and later p4p, using  the -e flag.

Chuck Karish   karish at well.com   (415) 317-0182

More information about the perforce-user mailing list