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 8BE58D1EBBD for ; Sun, 4 Apr 2004 13:04:13 +0000 (GMT) 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 67843-02 for ; Sun, 4 Apr 2004 10:04:32 -0300 (ADT) Received: from jinx.internetstaff.com (unknown [63.214.174.240]) by svr1.postgresql.org (Postfix) with ESMTP id 7E108D1EA61 for ; Sun, 4 Apr 2004 10:04:11 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by jinx.internetstaff.com (Postfix) with ESMTP id 0A04D4BC0C6 for ; Sun, 4 Apr 2004 06:04:36 -0700 (MST) Received: from jinx.internetstaff.com ([127.0.0.1]) by localhost (jinx [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 04831-03-10 for ; Sun, 4 Apr 2004 06:04:35 -0700 (MST) Subject: Re: PostgreSQL and Linux 2.6 kernel. From: Cott Lang To: pgsql-performance@postgresql.org In-Reply-To: <406FDBD2.9910.247F995@localhost> References: <406EA51B.21218.D2DE061@localhost> <406FDBD2.9910.247F995@localhost> Content-Type: text/plain Message-Id: <1081083874.2172.3.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-1) Date: Sun, 04 Apr 2004 06:04:35 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at internetstaff.com X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/32 X-Sequence-Number: 6332 On Sun, 2004-04-04 at 01:56, Gary Doades wrote: > Unfortunately I don't understand the question! > > My background is the primarily Win32. The last time I used a *nix OS > was about 20 years ago apart from occasional dips into the linux OS > over the past few years. If you can tell be how to find out what you want > I will gladly give you the information. There are two available io schedulers in 2.6 (new feature), deadline and anticipatory. It should show be listed in the boot messages: dmesg | grep scheduler I've seen people arguing for each of the two schedulers, saying one is better than the other for databases. I'm curious which one you're using. :)