[p4] Off-site Perforce performance/optimization
steve at vance.com
Wed Nov 1 21:40:24 PST 2006
This is a situation in which it can be beneficial to use compression
between the proxy and the server. You should make sure that the
bandwidth/CPU trade-off is worthwhile to you. If most of the content is
already compressed (images, etc.) then you won't see any benefit.
Jeff Desharnais wrote:
> We are currently running a Windows Server 2003 system with Perforce as
> our primary source control for about 110 people.
> We have a group of about 10 people across the country who need constant
> access to our source control.
> We have set them up with a proxy server that is caching any files as
> they are synchronized. We also have a client running on the proxy server
> that automatically syncs a few times a day to try and keep the cache up
> to date.
> Our users are still experiencing very poor performance with Perforce.
> File transfers, when not cached, are taking an extremely large amount of
> time and causing other problems such as client hangs.
> The servers are version 2005.2 and most clients are 2005.2, with a few
> running 2006.1.
> Are there any optimization tips you guys can share to help improve this
> Obviously, bandwidth is the major problem here for transfer times, but
> any optimization ideas would be greatly appreciated.
> Jeff Desharnais
> IT Specialist
> Mad Doc Software
> 100 Burtt Rd., Suite 220
> Andover, MA 01810
> (978) 409-6272 Ext. 132
> perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user