Date: Sun, 29 Aug 2004 15:49:45 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: obrien@freebsd.org Cc: current@freebsd.org Subject: Re: Public Access to Perforce? Message-ID: <41325D89.5040806@freebsd.org> In-Reply-To: <20040829223905.GB92947@dragon.nuxi.com> References: <200408160104.03708.chris@behanna.org> <20040826005527.GF54515@spiff.melthusia.org> <20040829223905.GB92947@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David O'Brien wrote: > On Wed, Aug 25, 2004 at 05:55:28PM -0700, Gordon Tetlow wrote: > >>Now Perforce performance demands that as much of the metadata in memory >>as possible. We are already starting to see the pressure with the >>operations that our developers are doing on the depot. When we ask >>Perforce support about ways to improve it, they generally tell us to >>throw more memory at the problem but we are limited in how far we can >>go with that (the box already has 2GB of memory in it). > > > Ask Perforce to port to 64-bit AMD64. That would allow them to have a > lot more memory for their in-memory operations. Another possibility would be to switch from Perforce to something like SVN. I'm not sure how it compares to Perforce, but SVN has much better branch and merge support than CVS does. It's also specifically designed for use over slow networks, which would be a real plus. Tim Kientzle
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41325D89.5040806>