Re: Subversion/Perforce timing statistics

If my understanding is correct, Perforce clients see their working
directories as NFS mounts, so that the Perforce server has control over
all filesystem operations (e.g. it can keep track of which files have
been modified so it never has to do a scan), and so that the working
directory and repository data are all in the same place.

It's not surprising that this would yield speed advantages, but it also
limits Perforce's ability to be used in some environments.

(Which is not to say that Subversion doesn't have performance overhead
issues. The import performance and database size are particularly
worrisome, and the checkout time isn't stellar either. 2-3 seconds for
update/commit probably isn't too bad; it depends on how well it scales
up.)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat May 25 17:31:30 2002