From owner-freebsd-current Wed Feb 17 8:58:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 4DD2010E66 for ; Wed, 17 Feb 1999 08:58:31 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA06486; Wed, 17 Feb 1999 08:58:30 -0800 (PST) (envelope-from dillon) Date: Wed, 17 Feb 1999 08:58:30 -0800 (PST) From: Matthew Dillon Message-Id: <199902171658.IAA06486@apollo.backplane.com> To: tcobb@staff.circle.net Cc: green@unixhelp.org, khetan@chain.freebsd.os.org.za, current@FreeBSD.ORG Subject: Re: RE: RE: Problems in VM structure ? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try reducing maxusers to 128. If you have mbuf problems, override NMBCLUSTERS ( making it 4096 or 8192 should be sufficient ). Sometimes network mbuf problems on heavily loaded machines are due to too-large default buffer sizes - if net.inet.tcp.sendspace or recvspace is greater then 16384, try reducing it to 16384. If your machine is not using that > 2GB of swap, cap the swap at 1.9GB. -Matt Matthew Dillon :I've had it at MAXUSERS=256 on both the P5 and the P6. The P5 stays :stable, the P6 doesn't. If I reduce MAXUSERS to 128 then these :heavily loaded boxen will fall over due to out of MBUFs errors, or :so I believe. : :I'd love to find some real kernel-tuning documentation out there, :one of my panics is a "pipeinit: cannot allocate pipe -- out of kvm" :and I can't pull a crashdump due to a DSCHECK error because my :SWAP is > 2GB. : : :-Troy Cobb : Circle Net, Inc. : http://www.circle.net : : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message