Date: Wed, 3 Aug 2005 20:52:16 -0600 From: Will Andrews <will@csociety.org> To: "mirrors@tds.net" <mirrors@tds.net> Cc: freebsd-hubs@freebsd.org Subject: Re: cvsupd on memfs/ramfs? Message-ID: <20050804025216.GI8060@hex.databits.net> In-Reply-To: <Pine.LNX.4.63.0508021325140.3273@gentoo2.workpc.tds.net> References: <XFMail.20050802085431.jdp@polstra.com> <Pine.LNX.4.63.0508021325140.3273@gentoo2.workpc.tds.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--PT0wT86ZVVq2zanE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 02, 2005 at 01:26:43PM -0500, mirrors@tds.net wrote: > What about running cvsupd using a ramfs? >=20 > What parts do you push to a RamFS, and how to you set it up to take a=20 > server reboot? I have 4 Gigs of ram and can commit like 2G to cvsupd. > I can install more if I can show it will be used well. Just configure the kern.maxvnodes sysctl as high as you can and let the VM cache handle pulling the most commonly accessed parts of the repository into memory. cvsup12 runs with this set to 200000, but you can probably do 250000 or 300000 or more since you can commit more memory than cvsup12 has. Just make sure to keep it from swapping. Regards, --=20 wca --PT0wT86ZVVq2zanE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFC8YLfF47idPgWcsURAn3qAJ4rFym79XHYxu49O63dilPjx3OjBgCgjIwo X1vOMhJHik3QV4y1w98YWKc= =VF7a -----END PGP SIGNATURE----- --PT0wT86ZVVq2zanE--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050804025216.GI8060>