From owner-freebsd-hackers Wed Jul 26 11:59:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 5971D37BEC5 for ; Wed, 26 Jul 2000 11:59:32 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id OAA79977; Wed, 26 Jul 2000 14:59:28 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 26 Jul 2000 14:59:28 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: =?iso-8859-1?q?Tommy=20Hallgren?= Cc: freebsd-hackers@freebsd.org Subject: Re: Benchmark oddities In-Reply-To: <20000726084402.23000.qmail@web119.yahoomail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I tend to agree with your comments on the benchmark, but have observed that when starting a large number of forks from the same parent on 4.0-STABLE, the system sporadically hangs waiting in vm_wait for some processes to exit, despite not having hit max kernel processes permitted, or hitting a per-user bound (user rwatson created 2k processes, and starved login running as root). I assume this is a vm limitation. Also, setting maxusers rediculously high (512, say) seems to result in a panic on 4.0 once you exceed a decent number of processes. Haven't had a chance to track any of this down however. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message