From owner-freebsd-hackers Thu Oct 28 16:43:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bomber.avantgo.com (ws1.avantgo.com [207.214.200.194]) by hub.freebsd.org (Postfix) with ESMTP id 979C8151B5 for ; Thu, 28 Oct 1999 16:43:30 -0700 (PDT) (envelope-from scott@avantgo.com) Received: from river ([10.0.128.30]) by bomber.avantgo.com (Netscape Messaging Server 3.5) with SMTP id 125; Thu, 28 Oct 1999 16:38:24 -0700 Message-ID: <15f901bf219e$20df55c0$1e80000a@avantgo.com> From: "Scott Hess" To: "Michael Beckmann" , "Mike Smith" Cc: References: <19991029011348.B2757@apfel.de> <199910282253.PAA02302@dingo.cdrom.com> <19991029020253.A3005@apfel.de> Subject: Re: Limitations in FreeBSD Date: Thu, 28 Oct 1999 16:42:42 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Beckmann wrote: > On Thu, Oct 28, 1999 at 03:53:20PM -0700, Mike Smith wrote: > > How severe is the performance > > penalty (have you actually measured it yet, or are you just going on > > word of mouth)? > > The latter. Measuring would be difficult due to lack of tools, and IŽd > rather not make life tests in production machines. Urk! I don't mean to be insulting, but the notion that you would roll _any_ solution out for a problem of this size based on word of mouth freaks the crap out of me. If you have a genuine need for 500Gig of news spool, and enough users that mmap'ed I/O in nntp is needed and the number of file descriptors is going to be a problem, and you're willing to change architectures if need be, then if you don't have tools - I'd suggest you write some! [And better to start early, because once you roll into production it's too late to write the tools :-),] scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message