Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id AE442632723 for ; Mon, 19 Jul 2010 11:38:39 -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 11530-06 for ; Mon, 19 Jul 2010 14:38:30 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by mail.postgresql.org (Postfix) with ESMTP id 2A8B16323FE for ; Mon, 19 Jul 2010 11:38:32 -0300 (ADT) Received: from [192.168.1.3] (static-71-179-240-8.bltmmd.fios.verizon.net [71.179.240.8]) by mrelayeu.kundenserver.de (node=mreu1) with ESMTP (Nemesis) id 0LhiSr-1PNeZS0Nov-00nFUY; Mon, 19 Jul 2010 16:38:24 +0200 Message-ID: <4C44635D.7080601@2ndquadrant.com> Date: Mon, 19 Jul 2010 10:38:21 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Daniel Ferreira de Lima CC: Kevin Grittner , pgsql-performance@postgresql.org Subject: Re: IDE x SAS RAID 0 on HP DL 380 G5 P400i controller performance problem References: <4C440C93020000250003388D@gw.wicourts.gov> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:yATxrOpnzHh9OrzeyOLg0L8odgjWMzhKBo/Pq59DLps SrtxF9Y+KPZ3O8ssRrQL3a3z93W31lZaBVdsDWwcVDEv5b8Twj 7dMWcwtVAE/0Ky9x4xQjtxSpq7VvehSZkOYU+vV9nWMdkXPlTu vFQO/PzrWkvRlMZX832jOTWCNXkG2vVRQUWHejF6OqVXSrossE mQIJhXn4BEWf5fNwDZNIEOhpQn1+RROikU5DGrgcu4= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.8 tagged_above=-10 required=5 tests=BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201007/284 X-Sequence-Number: 39673 Daniel Ferreira de Lima wrote: > > > > > **Both with Linux Kernel 2 .4.37.9 and Postgresql 7.2** > > Wow. You really need to upgrade. > > > Yes, but unfortunately, actually it's impossible and economically > inviable... Generally, getting good performance out of PostgreSQL 7.2 is also impossible and economically inviable. You can either put resources toward upgrading to a newer version, which will fix many of the performance issues here, or toward changes to the old version that are not guaranteed to actually improve anything. That said, a look into the write-caching+BBU policy on your controller is worthwhile. If you're running this application successfully on some hardware but not others, that could be a source for the difference. -- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.us