From owner-freebsd-net@FreeBSD.ORG Mon Jan 21 00:19:32 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00E0316A419 for ; Mon, 21 Jan 2008 00:19:32 +0000 (UTC) (envelope-from silby@silby.com) Received: from relay00.pair.com (relay00.pair.com [209.68.5.9]) by mx1.freebsd.org (Postfix) with SMTP id 9DC4E13C448 for ; Mon, 21 Jan 2008 00:19:31 +0000 (UTC) (envelope-from silby@silby.com) Received: (qmail 51698 invoked from network); 20 Jan 2008 23:52:50 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 20 Jan 2008 23:52:50 -0000 X-pair-Authenticated: 209.68.2.70 Date: Sun, 20 Jan 2008 17:52:50 -0600 (CST) From: Mike Silbersack To: s3raphi In-Reply-To: <14983301.post@talk.nabble.com> Message-ID: <20080120175048.H39017@odysseus.silby.com> References: <20070709234401.S29353@odysseus.silby.com> <14983301.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: FreeBSD 7 TCP syncache fix: request for testers 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: Mon, 21 Jan 2008 00:19:32 -0000 On Sun, 20 Jan 2008, s3raphi wrote: > I am running web polygraph against a FreeBSD7.0-RC1 squid server and > experiencing problems. I have run the same test against the same hardware on > FreeBSD 6.1 without issue. This seems to be specific to FreeBSD 7. > The problem is related to the number of client connections: > 250 Clients - runs great. > 500 Clients- scores well in polygraph, but does have a few errored requests > 750-2000 Clients - Error rate spikes way up and performance takes a > nosedive. > > This looks similar to what is described in this thread. Has your fix been > rolled in to RC1? The syncache in 7.0-RC1 has all known bugs fixed, so either you are encountering a new bug or simply having a lot of packet loss. Please try to use tcpdump to capture traffic while these errors are occuring, and include info as to whether you are using any firewalls of any sort anywhere in the connection. Then send that to me and I'll get to it as soon as I can, which may be a week from now. -Mike