From owner-freebsd-hackers Mon Apr 15 09:32:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA02371 for hackers-outgoing; Mon, 15 Apr 1996 09:32:48 -0700 (PDT) Received: from gytha.demon.co.uk (bpaj@gytha.demon.co.uk [158.152.166.246]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA02337 Mon, 15 Apr 1996 09:32:34 -0700 (PDT) Received: (from bpaj@localhost) by gytha.demon.co.uk (8.7.4/8.7.3) id RAA02103; Mon, 15 Apr 1996 17:32:21 +0100 Date: Mon, 15 Apr 1996 17:32:21 +0100 (BST) From: Bryn Paul Arnold Jones To: dyson@freebsd.org cc: Linus Torvalds , julian@ref.tfs.com, hackers@freebsd.org, linux-kernel@vger.rutgers.edu Subject: Re: Unices are created equal, but ... In-Reply-To: <199604151348.IAA09000@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 15 Apr 1996, John S. Dyson wrote: [...] > > If somebody wants to do benchmarking,I'd suggest using at least > > - lmbench (nice microbenchmark) > > - bonnie (reasonable disk performance benchmark) > > - webstone (or something similar. But use "apache" as the server, not > > some braindead horror like NCSA). > > - ??? > > > Above list is ok, but CERTAINLY not sufficient. > > > (the three mentioned should cover different areas, all very reasonable, > > but have I missed some important area?) > > > Above list has no testing under VM load. That is where memory scheduling > policies start taking effect. There are other forms of loading also, like > tty subsystems (some people still use those.) Another, is how well do big disk > farms work (lots of sustained concurrent I/O)? How does the system work > with many many TCP connections (little benchmarks like lmbench are interesting > but don't show performance in an ISP or large workstation situation)? > > John > How about running those three at the same time, it sould put the box under some considerable load. Bryn -- PGP key pass phrase forgotten, \ Overload -- core meltdown sequence again :( | initiated. / This space is intentionally left | blank, apart from this text ;-) \____________________________________