From deeff608bac052647edc154446024c0cf9850813 Mon Sep 17 00:00:00 2001 From: Giorgos Keramidas Date: Sun, 14 Apr 2002 02:00:51 +0000 Subject: [PATCH] Reword MFS stuff in the system requirements section. Also expand the RAID disk paragraph and add some stuff about SCSI controllers that might help speeding up things. PR: docs/37037 Submitted by: Dominic Marks --- en_US.ISO8859-1/articles/hubs/article.sgml | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/en_US.ISO8859-1/articles/hubs/article.sgml b/en_US.ISO8859-1/articles/hubs/article.sgml index 24502708cd..357332b1ea 100644 --- a/en_US.ISO8859-1/articles/hubs/article.sgml +++ b/en_US.ISO8859-1/articles/hubs/article.sgml @@ -97,15 +97,24 @@ CVSup, rsync or even AnonCVS. This can have a huge impact on CPU and memory requirements. Especially rsync is considered a memory hog, and CVSup does - indeed consume some CPU. For AnonCVS it can - even be required to set up a MFS of at least + indeed consume some CPU. For AnonCVS it might + be a nice idea to set up a memory resident filesystem (MFS) of at least 300 MB, so you need to take this into account for your memory requirements. You also want to consider a fast disk subsystem. Operations on the CVS repository require a fast - disk subsystem (RAID is greatly advised). + disk subsystem (RAID is greatly advised). A SCSI + controller that has a cache of its own can also + speed up things, since most of these services incur a + very large number of small modifications to the disk. + + You can also experiment with enlarging the portion + of system memory which is used for the filesystem buffer cache. + This will also help to reduce the quantity of disk access. This + can be done with the BUFCACHEPERCENT kernel option. The default is + to use 5% of system memory.