os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Reword MFS stuff in the system requirements section.

Browse source 
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 <dominic_marks@btinternet.com>
This commit is contained in:
Giorgos Keramidas 2002-04-14 02:00:51 +00:00
parent 23be42b06b
commit deeff608ba
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=12784
1 changed files with 12 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
en_US.ISO8859-1/articles/hubs/article.sgml
View file

@ -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.
</para>
<para>
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.
</para>
<para>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.
</para>
</sect2>
<sect2 id="mirror-services">