Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 89AB1637A93 for ; Mon, 12 Jul 2010 12:38: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 37611-04-4 for ; Mon, 12 Jul 2010 15:38:36 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by mail.postgresql.org (Postfix) with ESMTP id 5DEAC6353C1 for ; Mon, 12 Jul 2010 12:23:22 -0300 (ADT) Received: from [75.192.140.165] (165.sub-75-192-140.myvzw.com [75.192.140.165]) by mrelayeu.kundenserver.de (node=mrbap2) with ESMTP (Nemesis) id 0M5IbP-1PJ0SP48vH-00zYqS; Mon, 12 Jul 2010 17:23:19 +0200 Message-ID: <4C3B3364.2040101@2ndquadrant.com> Date: Mon, 12 Jul 2010 11:23:16 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Ryan Wexler CC: pgsql-performance@postgresql.org Subject: Re: performance on new linux box References: <4C3532CC.6070601@squeakycode.net> <4C3591F40200002500033219@gw.wicourts.gov> <4C35A23B0200002500033220@gw.wicourts.gov> <4C36E6FC.6030902@pws.com.au> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:9fXm4q0pJ4g/YV/hj+6fhEkWsl45SvRkTWD+Lpk6oUQ 6EJUBLdv3fWOeTSQ6KpHTDcly6vOXf4oHVL7+gP9MWkKVDmSoH wEiDvDL0m9iJhnkB98JG/C8JeMlXdoTVaJlFMVy780FRn8WhL/ bswwB6Oh2APoTl51wAGjOWdcOCs/Y2iYbE+woqddvQKr52+2rP WNY9h0ml5jS3VhMzYTZr0nJW6R03pMi+uxhZQtrAis= 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: 201007/199 X-Sequence-Number: 39588 Ryan Wexler wrote: > One question I do have is this card has a setting called Read Policy > which apparently helps with sequentially reads. Do you think that is > something I should enable? Linux will do some amount of read-ahead in a similar way on its own. You run "blockdev --getra" and "blockdev --setra" on each disk device on the system to see the settings and increase them. I've found that tweaking there, where you can control exactly the amount of readahead, to be more effective than relying on the less tunable Read Policy modes in RAID cards that do something similar. That said, it doesn't seem to hurt to use both on the LSI card you have; giving more information there to the controller for its use in optimizing how it caches things, by changing to the more aggressive Read Policy setting, hasn't ever degraded results significantly when I've tried. -- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.us