Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 6 Aug 2002 11:17:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 6 Aug 2002 11:17:26 -0400 Received: from garrincha.netbank.com.br ([200.203.199.88]:23826 "HELO garrincha.netbank.com.br") by vger.kernel.org with SMTP id ; Tue, 6 Aug 2002 11:17:25 -0400 Date: Tue, 6 Aug 2002 11:20:04 -0300 (BRT) From: Rik van Riel X-X-Sender: riel@imladris.surriel.com To: Steven Cole cc: Andrew Morton , Bill Davidsen , Marcelo Tosatti , Jens Axboe , lkml Subject: Re: Linux v2.4.19-rc5 In-Reply-To: <1028642837.2802.59.camel@spc9.esa.lanl.gov> Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1302 Lines: 39 On 6 Aug 2002, Steven Cole wrote: > That last one looks like the biggest cheat. Rather than optimizing for > dbench, is there a set of pessimizing numbers which would optimally turn > dbench into a semi-useful tool for measuring meaningful IO performance? > Or is dbench really only useful for stress testing? Yes, dbench is only useful as a stress testing tool. A minor varation in kernel behaviour can change dbench throughput by an order of magnitude and I'm not talking about any specific kernel component here ... ANY kernel component could trigger it. While it is easy to measure dbench throughput, it is nearly impossible to: 1) analyse why dbench throughput changed from kernel to kernel 2) predict the relation (if any) these changes in dbench throughput have with changes in performance of real applications, if any 3) identify which kernel subsystem was responsible for the change in dbench performance regards, Rik -- Bravely reimplemented by the knights who say "NIH". http://www.surriel.com/ http://distro.conectiva.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/