From owner-freebsd-hackers  Mon Dec  2 20:21:56 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id UAA06371
          for hackers-outgoing; Mon, 2 Dec 1996 20:21:56 -0800 (PST)
Received: from suburbia.net (suburbia.net [203.4.184.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA06358
          for <hackers@freebsd.org>; Mon, 2 Dec 1996 20:21:49 -0800 (PST)
Received: (from proff@localhost)
          by suburbia.net (8.8.3/8.8.2) id PAA15467;
          Tue, 3 Dec 1996 15:20:06 +1100 (EST)
From: Julian Assange <proff@suburbia.net>
Message-Id: <199612030420.PAA15467@suburbia.net>
Subject: Re: TCP/IP bandwidth bragging
In-Reply-To: <199612030319.VAA25727@brasil.moneng.mei.com> from Joe Greco at "Dec 2, 96 09:19:50 pm"
To: jgreco@brasil.moneng.mei.com (Joe Greco)
Date: Tue, 3 Dec 1996 15:20:06 +1100 (EST)
Cc: hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Look, folks, benchmarks are benchmarks.  They are not
> real world performance indicators.  They are simply
> relative artificial performance evaluators, and as 
> such can be influenced by a wide variety of factors,
> including OS tweaks.  I never make the mistake of 
> taking a benchmark's results as an absolute comparison
> of apples and oranges.
> 

Bench marks are not totally useless. Quite often it is hard to find
bottle necks without them. "The system feels slower" isn't going
to do you much good as a diagnostic tool with a monolithic kernel.
This does not imply that they find all bottle-necks.

Julian A.