From owner-freebsd-current Sat Nov 2 10: 3: 5 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2853537B401 for ; Sat, 2 Nov 2002 10:03:04 -0800 (PST) Received: from web14108.mail.yahoo.com (web14108.mail.yahoo.com [216.136.172.138]) by mx1.FreeBSD.org (Postfix) with SMTP id D3D2E43E4A for ; Sat, 2 Nov 2002 10:03:03 -0800 (PST) (envelope-from galen_sampson@yahoo.com) Message-ID: <20021102180303.58968.qmail@web14108.mail.yahoo.com> Received: from [209.245.140.235] by web14108.mail.yahoo.com via HTTP; Sat, 02 Nov 2002 10:03:03 PST Date: Sat, 2 Nov 2002 10:03:03 -0800 (PST) From: Galen Sampson Subject: Re: crash with network load (in tcp syncache ?) To: Terry Lambert Cc: current@freebsd.org In-Reply-To: <3DC3ABA0.97988F96@mindspring.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi --- Terry Lambert wrote: > With proper tuning, and some minor patches, 7000/second isn't hard > to get. > > If you add the Duke University version of the Rice University patches > for LRP, modify the mbuf allocator for static freelisting and then > pre-populate it, and tune the kernel properly, you should be able to > get over 20,000 connections per second. The best I've managed with a > modified FreeBSD 4.2, before the SYN-cache code, was 32,000/second. Out of pure curiosity what is the reason that the Duke and Rice patches were never incorporated into the base system. If it really enables the same machine to provide 4 times the number of connections this seems like it would be a useful thing to include. regards, Galen Sampson __________________________________________________ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message