Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id B3273632E12 for ; Tue, 9 Feb 2010 00:16:32 -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 54300-03 for ; Tue, 9 Feb 2010 04:16:22 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mail.postgresql.org (Postfix) with ESMTP id E65586329CA for ; Tue, 9 Feb 2010 00:16:21 -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=mreu1) with ESMTP (Nemesis) id 0MAysS-1NWyIF0YJ2-00A74f; Tue, 09 Feb 2010 05:16:17 +0100 Message-ID: <4B70E18D.2040709@2ndquadrant.com> Date: Mon, 08 Feb 2010 23:16:13 -0500 From: Greg Smith User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Hannu Krosing CC: 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> In-Reply-To: <1265652529.2153.13.camel@hvost> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX19uLJgkX2mKd8CAJ5q5RVMdeQrk+WEWM+vcVEB 6LG4xfmoigoWj4Su2fEsmDIUW29TPp2A1DmLMM8pj3OZn78Hdc /fsilDds69C9fMYJjp1cBNKojv+6KHZ X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.418 tagged_above=-10 required=5 tests=AWL=0.181, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201002/129 X-Sequence-Number: 37550 Hannu Krosing wrote: > Have you kept trace of what filesystems are in use ? > Almost everything I do on Linux has been with ext3. I had a previous diversion into VxFS and an upcoming one into XFS that may shed more light on all this. And, yes, the whole I/O scheduling approach in Linux was just completely redesigned for a very recent kernel update. So even what we think we know is already obsolete in some respects. -- Greg Smith 2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.com