From owner-freebsd-hackers Thu Oct 28 16:41:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 484D7151B5 for ; Thu, 28 Oct 1999 16:41:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id QAA02494; Thu, 28 Oct 1999 16:32:03 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910282332.QAA02494@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Michael Beckmann Cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD In-reply-to: Your message of "Fri, 29 Oct 1999 02:02:53 +0200." <19991029020253.A3005@apfel.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Thu, 28 Oct 1999 16:32:03 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, Oct 28, 1999 at 03:53:20PM -0700, Mike Smith wrote: > > How many fd's do you plan to have open? > = > This would be 2^17 to 2^19. Would that be advisable ? I have never > seen anything like that. That would be difficult. > > 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=B4= d > rather not make life tests in production machines. This is a failure of your approach, I think. You are trying to make a = decision without adequate information, which is never a good idea. = Craft the tools and make an informed choice. TBH, it sounds like you need to look at a different reader architecture. -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message