From owner-freebsd-hackers Sat Dec 18 14:26:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 1B41F14D31 for ; Sat, 18 Dec 1999 14:26:28 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 8A7791CD0; Sun, 19 Dec 1999 06:04:24 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Kevin Day Cc: rfg@monkeys.com (Ronald F. Guilmette), hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? In-Reply-To: Message from Kevin Day of "Sat, 18 Dec 1999 14:58:09 CST." <199912182058.OAA42531@celery.dragondata.com> Date: Sun, 19 Dec 1999 06:04:24 +0800 From: Peter Wemm Message-Id: <19991218220424.8A7791CD0@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kevin Day wrote: > > In message <199912181944.NAA68434@celery.dragondata.com>, you wrote: > > > > >What's the practical number of TCP connections per server? > > > > I've gotten over 8,000 at one time on one FreeBSD box. I'm aware of boxes having been tested to ~100,000 connections if my memory serves correctly. I know there were problems going over 64k connections at one point due to a 16 bit reference counter in the routes. > > The way to solve that is to include calls to setsockopt() in your server > > that will have the effect of reducing the per-connection I/O buffer sizes > > just after you accept() each new connection. > > Speaking of accepting... What's the upper limit on listen queues? Something > around 64, correct? Tuneable: peter@overcee[6:00am]~src/sys/kern-244> sysctl kern.ipc.somaxconn kern.ipc.somaxconn: 128 Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message