From owner-freebsd-net  Fri Jul 17 13:07:06 1998
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA11285
          for freebsd-net-outgoing; Fri, 17 Jul 1998 13:07:06 -0700 (PDT)
          (envelope-from owner-freebsd-net@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11267
          for <freebsd-net@FreeBSD.ORG>; Fri, 17 Jul 1998 13:07:04 -0700 (PDT)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id NAA15523;
	Fri, 17 Jul 1998 13:06:27 -0700 (PDT)
Message-Id: <199807172006.NAA15523@implode.root.com>
To: Mark Powell <M.S.Powell@ais.salford.ac.uk>
cc: freebsd-net@FreeBSD.ORG
Subject: Re: 2.2.6 net performance and panic with 1000's of sockets open 
In-reply-to: Your message of "Fri, 17 Jul 1998 15:49:31 BST."
             <Pine.BSF.3.96.980717154849.1098A-100000@plato.salford.ac.uk> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Fri, 17 Jul 1998 13:06:27 -0700
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>  Using another test program I found that FreeBSD would panic. The program
>opened 1000 sockets to the squid box and requested a file from the web
>through each. The machine would panic with a page fault everytime I ran

   You need more networking buffers. Something like:

options "NMBCLUSTERS=8000"

   might work, but this depends on how large the socket buffers are for each
of the open connections. Later versions of FreeBSD will panic immediately
when running out of buffers, rather than panicing randomly a few seconds
later.

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message