Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 6E50E632DE5 for ; Wed, 10 Feb 2010 22:09:42 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 93284-06 for ; Thu, 11 Feb 2010 02:09:23 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mail.postgresql.org (Postfix) with ESMTP id 7E76C632D9A for ; Wed, 10 Feb 2010 22:09:31 -0400 (AST) Received: from [192.168.0.105] (pool-96-244-14-10.bltmmd.fios.verizon.net [96.244.14.10]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0MK5kP-1NgDRO25GX-002779; Thu, 11 Feb 2010 03:09:26 +0100 Message-ID: <4B7366D2.6040308@2ndquadrant.com> Date: Wed, 10 Feb 2010 21:09:22 -0500 From: Greg Smith User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: david@lang.hm CC: Scott Marlowe , Jeff , Hannu Krosing , Kevin Grittner , pgsql-performance@postgresql.org, Albe Laurenz Subject: Re: Linux I/O tuning: CFQ vs. deadline References: <4B6FDD26.9010106@2ndquadrant.com> <4B6FD868020000250002F084@gw.wicourts.gov> <4B702E05.1000708@2ndquadrant.com> <1265652529.2153.13.camel@hvost> <4B70E18D.2040709@2ndquadrant.com> <39DDB34B-C375-46ED-83D2-688A32188100@torgo.978.org> <4B725410.5010000@2ndquadrant.com> <4B73615B.6060700@2ndquadrant.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1+zkVuT4RCSAO9wUs4PDTStIXL3VAxI5ptwLd1 cJeY1SFNze+j4CfCIZxTnjkYMyf8b70UCkEgvRrdSKuAhGLaIk nKpyr3Jd61i6p8NlZd6Gxdjf9HffFwj X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.42 tagged_above=-10 required=5 tests=AWL=0.179, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201002/177 X-Sequence-Number: 37598 david@lang.hm wrote: > most of my new hardware has no problems with the old kernels as well, > but once in a while I run into something that doesn't work. Quick survey just of what's within 20 feet of me: -Primary desktop: 2 years old, requires 2.6.23 or later for SATA to work -Server: 3 years old, requires 2.6.22 or later for the Areca card not to panic under load -Laptops: both about 2 years old, and require 2.6.28 to work at all; mostly wireless issues, but some power management ones that impact the processor working right too, occasional SATA ones too. I'm looking into a new primary desktop to step up to 8 HT cores; I fully expect it won't boot anything older than 2.6.28 and may take an even newer kernel just for basic processor and disks parts to work. We're kind of at a worst-case point right now for this sort of thing, on the tail side of the almost 3 year old RHEL5 using a 3.5 year old kernel as the standard for so many Linux server deployments. Until RHEL6 is ready to go, there's little motivation for the people who make server hardware to get all their drivers perfect in the newer kernels. Just after that ships will probably be a good time to do that sort of comparison, like it was possible to easily compare RHEL4 using 2.6.9 and RHEL5 with 2.6.18 easily in mid to late 2007 with many bits of high-performance hardware known to work well on each. -- Greg Smith 2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.com