Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id A3C631337B53 for ; Tue, 12 Oct 2010 03:39:44 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 83422-08 for ; Tue, 12 Oct 2010 06:39:37 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by mail.postgresql.org (Postfix) with ESMTP id C3FFA1336705 for ; Tue, 12 Oct 2010 03:39:36 -0300 (ADT) Received: from [192.168.1.7] (static-71-179-240-8.bltmmd.fios.verizon.net [71.179.240.8]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0MhNhq-1PJOBI0pQw-00My8Z; Tue, 12 Oct 2010 08:39:35 +0200 Message-ID: <4CB402A4.9070109@2ndquadrant.com> Date: Tue, 12 Oct 2010 02:39:32 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Samuel Gendler CC: Joshua Tolley , Craig Ringer , mladen.gogala@vmsinfo.com, Neil Whelchel , "pgsql-performance@postgresql.org" Subject: Re: Slow count(*) again... References: <201010091626.18636.neil.whelchel@gmail.com> <4CB11CC7.8070300@vmsinfo.com> <4CB167CA.9070109@postnewspapers.com.au> <4CB1F46E.80205@vmsinfo.com> <4CB2410C.6010603@postnewspapers.com.au> <4cb25a0e.2a978e0a.7797.33d6@mx.google.com> <4CB3C598.2010302@2ndquadrant.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:BFN+IUjQMbwlnKaYl6n3n2H4qI7H5D5HzsMW6IJF1gM 6VJKdugzUf5nJ/R5kKEsrQQtorxEqSbDLU4LS3iVqQKPtu2Tx8 p0AgQSufyMwzYrIiA8X4r9Q0mEAoTWtQuSTquLnStfxBu7K19u 8nsS3EOHLvXt3I9+EUmvsZddaSaqZGeWskWR5G5t9HV9rJ0PuU Pt0OwckKpwM8JxMIYgNZG8L0Ebapvr4eFpsE/JCVzo= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201010/133 X-Sequence-Number: 40552 Samuel Gendler wrote: > I spent some time going through the various tuning docs on the wiki > whie bringing some new hardware up and I can't remember seeing any > discussion of tweaking read-ahead at all in the normal > performance-tuning references. Do you have any documentation of the > kinds of tweaking you have done and its effects on different types of > workloads? Much of my recent research has gone into the book you'll see plugged below rather than the wiki. The basics of read-ahead tuning is that you can see it increase bonnie++ sequential read results when you increase it, to a point. Get to that point and stop and you should be in good shape. -- Greg Smith, 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services and Support www.2ndQuadrant.us Author, "PostgreSQL 9.0 High Performance" Pre-ordering at: https://www.packtpub.com/postgresql-9-0-high-performance/book