Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 6 Aug 2002 10:44:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 6 Aug 2002 10:44:49 -0400 Received: from garrincha.netbank.com.br ([200.203.199.88]:18698 "HELO garrincha.netbank.com.br") by vger.kernel.org with SMTP id ; Tue, 6 Aug 2002 10:44:46 -0400 Date: Tue, 6 Aug 2002 09:59:17 -0300 (BRT) From: Rik van Riel X-X-Sender: riel@imladris.surriel.com To: Bill Davidsen cc: Steven Cole , Marcelo Tosatti , Jens Axboe , lkml , Andrew Morton , Steven Cole Subject: Re: Linux v2.4.19-rc5 In-Reply-To: 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: 1226 Lines: 33 On Mon, 5 Aug 2002, Bill Davidsen wrote: > > Here are some dbench numbers, from the "for what it's worth" department. > > Call me an optimist, but after all the reliability problems we had win the > 2.5 series, I sort of hoped it would be better in performance, not > increasingly worse. Am I misreading this? Can we fall back to the faster > 2.4 code :-( Dbench is at its best when half (or more) of the dbench processes are stuck semi-infinitely in __get_request_wait and the others can operate in RAM without ever touching the disk. In effect, if you want the best dbench throughput you should make the system completely unsuitable for real world applications ;) There are a few things that are good for both real world performance and dbench performance, but those are easily dwarved by random factors like IO scheduling, timeslice length, etc... 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/