Date: Wed, 5 Sep 2001 23:03:37 +0000 (UTC) From: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-current@freebsd.org Subject: Re: more anoncvs servers Re: none Message-ID: <9n6b09$mvv$1@kemoauc.mips.inka.de> References: <F209GUjGnAKYoo9tjxq000052dc@hotmail.com> <20010905094236.G96880@dragon.nuxi.com> <200109051754.f85HsKH07526@vashon.polstra.com> <20010905124000.A1804@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David O'Brien <obrien@freebsd.org> wrote: > > - You need a pretty powerful machine to handle even, say, 4-6 clients > > at a time. Anonymous CVS is a hog like you wouldn't believe. > > I have to wonder if there are tricks one can use. No. Get a gig of memory, and put ~anoncvs/tmp on a memory disk. A monster of a fast disk system, RAID with lots of disks, also helps. > The GCC and OpenBSD people depend on anoncvs as their main repo transport > mechanism. (You can't transport a repo with cvs. OpenBSD infrastructure currently uses a grown mix of sup, cvsup, cvs, and rsync.) > I would imagine there are more than 4-6 people using their > anoncvs services at times. Speaking for OpenBSD, these are either big machines, or anoncvs is real slow. There were times when src or ports tree updates took all night. John may have exaggerated a bit, but anoncvs is indeed a hog. grappa.unix-ag.uni-kl.de is a pentium-100, 64M box. We used to experimentally run with MFS, because OpenBSD prior to 2.9 didn't have reliable soft updates, and the box basically ran from swap. Nowdays, ~anoncvs/tmp is back on disk. Single spindle. The disk hasn't exploded yet, but with, say, three anoncvs clients in parallel, it sure is maxed out. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9n6b09$mvv$1>