X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 892A4D1D370 for ; Tue, 6 Apr 2004 10:00:42 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 21737-06 for ; Tue, 6 Apr 2004 10:01:27 -0300 (ADT) Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by svr1.postgresql.org (Postfix) with ESMTP id 0935AD1D282 for ; Tue, 6 Apr 2004 10:00:39 -0300 (ADT) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-32.mail.demon.net with esmtp (Exim 3.35 #1) id 1BAqCk-000IEF-0W for pgsql-performance@postgresql.org; Tue, 06 Apr 2004 14:01:26 +0100 Received: by mainbox.archonet.com (Postfix, from userid 529) id 77BDE1799E; Tue, 6 Apr 2004 14:01:25 +0100 (BST) Received: from client17.archonet.com (client17.archonet.com [192.168.1.17]) by mainbox.archonet.com (Postfix) with ESMTP id 23E1216486 for ; Tue, 6 Apr 2004 14:01:23 +0100 (BST) From: Richard Huxton To: pgsql-performance@postgresql.org Subject: Back to Linux 2.6 kernel thoughts... Date: Tue, 6 Apr 2004 14:01:23 +0100 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200404061401.23189.dev@archonet.com> X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=0.15.3 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/60 X-Sequence-Number: 6360 I seem to remember discussion of anticipatory vs deadline scheduler in 2.6. Here is what Andrew Morton (I think) says: "The deadline scheduler has two additional scheduling queues that were not available to the 2.4 IO scheduler. The two new queues are a FIFO read queue and a FIFO write queue. This new multi-queue method allows for greater interactivity by giving the read requests a better deadline than write requests, thus ensuring that applications rarely will be delayed by read requests. Deadline scheduling is best suited for database servers and high disk performance systems. Morton has experienced up to 15 percent increases on database loads while using deadline scheduling." http://story.news.yahoo.com/news?tmpl=story&cid=75&e=2&u=/nf/20040405/tc_nf/23603 Nothing very in-depth in the story. -- Richard Huxton Archonet Ltd