From owner-freebsd-net@FreeBSD.ORG Sat Nov 10 09:41:01 2007 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0975C16A41B for ; Sat, 10 Nov 2007 09:41:01 +0000 (UTC) (envelope-from silby@silby.com) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.freebsd.org (Postfix) with SMTP id 9454613C4AC for ; Sat, 10 Nov 2007 09:41:00 +0000 (UTC) (envelope-from silby@silby.com) Received: (qmail 99251 invoked from network); 10 Nov 2007 09:40:39 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 10 Nov 2007 09:40:39 -0000 X-pair-Authenticated: 209.68.2.70 Date: Sat, 10 Nov 2007 03:40:38 -0600 (CST) From: Mike Silbersack To: Matt Reimer In-Reply-To: Message-ID: <20071110033704.D46803@odysseus.silby.com> References: <20071109213846.O46803@odysseus.silby.com> <20071110020333.I46803@odysseus.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: net@freebsd.org Subject: Re: Should syncache.count ever be negative? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2007 09:41:01 -0000 On Sat, 10 Nov 2007, Matt Reimer wrote: > I ran "netstat -Lan" every second while running this test and the > output never changed from the following, whether before or after the > stall: I forgot to mention, check netstat -s for listen queue overflows. > During the stall the sockets are all in TIME_WAIT. More relevant info: In the past that was not a problem, but I should retest this as well. > It still stalls. This time I noticed that tcptw shows 0 free: The tcptw zone is supposed to fill completely, then kick out the oldest entry whenever a new one comes in. So, that sounds ok to me... but like I said, I need to retest that too. > When I use ab I'm telling it to use a max of 100 simultaneous > connections (ab -c 100 -n 50000 http://66.230.193.105/). Wouldn't that > be well under the limit? Yep, should be. Hmph. -Mike