On Thu, 14 Dec 2000, Pyatt, Scott wrote:
> Bottlenecks to the CVS server are usually, in order of severity, network,
> disk I/O and finally CPU (sometimes memory). Having a good admin that can
> monitor what is happening and make the appropriate tuning tweaks and
> recommendations is invaluable.
Actually, you'll probably hit I/O long before you hit network or
CPU. We found, at least using pserver, that making /tmp (or wherever
pserver will place its temp files) a memory-backed FS was much faster than
when it was disk-based, as pserver makes a copy of everything it's about
to send to /tmp, and that means making lots of small files very quickly,
then deleting them. One optimization to pserver IMHO would be to have it
build a single file to transfer instead of lots of small ones, if that is
possible.
Brian
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
