Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752574AbYJ0LeW (ORCPT ); Mon, 27 Oct 2008 07:34:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752251AbYJ0LeL (ORCPT ); Mon, 27 Oct 2008 07:34:11 -0400 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:50507 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751689AbYJ0LeK (ORCPT ); Mon, 27 Oct 2008 07:34:10 -0400 Date: Mon, 27 Oct 2008 11:33:06 +0000 From: Alan Cox To: Ingo Molnar Cc: Jiri Kosina , Andrew Morton , Peter Zijlstra , Mike Galbraith , David Miller , rjw@sisk.pl, s0mbre@tservice.net.ru, linux-kernel@vger.kernel.org, netdev@vger.kernel.org Subject: Re: [tbench regression fixes]: digging out smelly deadmen. Message-ID: <20081027113306.5b1d5898@lxorguk.ukuu.org.uk> In-Reply-To: <20081027112750.GA2771@elte.hu> References: <20081024.221653.23695396.davem@davemloft.net> <1224914333.3822.18.camel@marge.simson.net> <1224917623.4929.15.camel@marge.simson.net> <20081025.002420.82739316.davem@davemloft.net> <1225010790.8566.22.camel@marge.simson.net> <1225011648.27415.4.camel@twins> <20081026021153.47878580.akpm@linux-foundation.org> <20081027112750.GA2771@elte.hu> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.12; x86_64-redhat-linux-gnu) Organization: Red Hat UK Cyf., Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, Y Deyrnas Gyfunol. Cofrestrwyd yng Nghymru a Lloegr o'r rhif cofrestru 3798903 Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1172 Lines: 28 > The way to get the best possible dbench numbers in CPU-bound dbench > runs, you have to throw away the scheduler completely, and do this > instead: > > - first execute all requests of client 1 > - then execute all requests of client 2 > .... > - execute all requests of client N Rubbish. If you do that you'll not get enough I/O in parallel to schedule the disk well (not that most of our I/O schedulers are doing the job well, and the vm writeback threads then mess it up and the lack of Arjans ioprio fixes then totally screw you) > the moment the clients are allowed to overlap, the moment their requests > are executed more fairly, the dbench numbers drop. Fairness isn't everything. Dbench is a fairly good tool for studying some real world workloads. If your fairness hurts throughput that much maybe your scheduler algorithm is just plain *wrong* as it isn't adapting to workload at all well. Alan -- 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/