Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 1E5C863275E for ; Thu, 24 Jun 2010 10:58:02 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 57159-03 for ; Thu, 24 Jun 2010 13:57:53 +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 F0FFA6322D5 for ; Thu, 24 Jun 2010 10:57:54 -0300 (ADT) Received: from [75.192.5.210] (210.sub-75-192-5.myvzw.com [75.192.5.210]) by mrelayeu.kundenserver.de (node=mrbap2) with ESMTP (Nemesis) id 0MDEgG-1OQfwS1ldM-00GYZT; Thu, 24 Jun 2010 15:57:53 +0200 Message-ID: <4C23645E.5070101@2ndquadrant.com> Date: Thu, 24 Jun 2010 09:57:50 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Janning CC: pgsql-performance@postgresql.org Subject: Re: Write performance References: <201006241443.33296.ml@planwerk6.de> In-Reply-To: <201006241443.33296.ml@planwerk6.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1+EPURlkcOUiXMqb6MATg6yEW3UINqHqPh9BXf XOU1K3gUfoN/GZCxUA0hgtPI9VCyQ2m8NMWe58ImGjmR6C95gg gVCYQ5hkqvvlI6LfNxGb1Sdh/fIYSGF X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.001 tagged_above=-10 required=5 tests=BAYES_20=-0.001, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201006/429 X-Sequence-Number: 39285 As others have already pointed out, your disk performance here is completely typical of a single pair of drives doing random read/write activity. So the question you should be asking is how to reduce the amount of reading and writing needed to run your application. The suggestions at http://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server address that. Increases to shared_buffers and checkpoint_segments in particular can dramatically reduce the amount of I/O needed to run an application. On the last server I turned, random reads went from a constant stream of 1MB/s (with default value of shared_buffers at 32MB) to an average of 0.1MB/s just by adjusting those two parameters upwards via those guidelines. If you haven't already made large increases to those values, I'd suggest starting there before presuming you must get a different disk setup. -- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.us