From owner-freebsd-current Mon Oct 5 08:27:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23980 for freebsd-current-outgoing; Mon, 5 Oct 1998 08:27:07 -0700 (PDT) (envelope-from owner-freebsd-current@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 IAA23960 for ; Mon, 5 Oct 1998 08:26:54 -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 IAA12441; Mon, 5 Oct 1998 08:26:04 -0700 (PDT) Message-Id: <199810051526.IAA12441@implode.root.com> To: "Mikhail A. Sokolov" cc: current@FreeBSD.ORG Subject: Re: -current panics.. In-reply-to: Your message of "Mon, 05 Oct 1998 18:31:42 +0400." <19981005183142.59994@demos.su> From: David Greenman Reply-To: dg@root.com Date: Mon, 05 Oct 1998 08:26:04 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It comes out (once again, emprecially) that this is somehow caused >by NMBCLUSTERS being >12288. Strange, since I recall wcarchive has it set to >1024*48 or something, right? Wcarchive does NOT run a standard kernel. It has various tweaks, such as greatly expanded kernel virtual address space, which are specific to that machine and not appropriate for 99.999% of FreeBSD users. NMBCLUSTERS on wcarchive is currently set to 80000, but will need to be doubled again to 160000 before we can support 10000 concurrent users. The VM is evenly split for 2GB for user processes and 2GB for the kernel (contrast that with standard FreeBSD which is 3.75GB user and .25GB kernel). -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message