Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 1F9A2B5DC26 for ; Mon, 22 Aug 2011 13:53:11 -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 57077-07 for ; Mon, 22 Aug 2011 16:53:04 +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 0DE64B5DC23 for ; Mon, 22 Aug 2011 13:53:04 -0300 (ADT) Received: from [192.168.1.7] (mail.highperformancepostgresql.com [71.179.240.8]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0MVJxm-1QlDBj1YjO-00YMiV; Mon, 22 Aug 2011 18:53:02 +0200 Message-ID: <4E52896C.1030202@2ndQuadrant.com> Date: Mon, 22 Aug 2011 12:53:00 -0400 From: Greg Smith User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110702 Icedove/3.0.11 MIME-Version: 1.0 To: Midge Brown CC: pgsql-performance@postgresql.org Subject: Re: settings input for upgrade References: <4E515A69.6050709@2ndQuadrant.com> <2DF9D6EED638438A995A442C05D54688@BERNICE> In-Reply-To: <2DF9D6EED638438A995A442C05D54688@BERNICE> Content-Type: multipart/alternative; boundary="------------030203020608070305090407" X-Provags-ID: V02:K0:VijGD1Pbia2pRXGME/i+ofT5LaI1uvEPirpGhbjXZB0 fwqQYoA4Rj86lftmbZq7OLcv5CuO0jqIbK9tCEsoVVJShP9QYm ClBMcCOzqnvl2MQFnzK2XQoTowS12B2YeCvgDBiJ57tvDEvRxu XR487znmQ5IF54NVX+W+YT6g9ey7VLTW5COJmpiIoEMn2u4tn+ TwQRME2TDouSZ2W8u4soFVt/GFsfMpjtfv5cqwpL/U= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.899 tagged_above=-10 required=5 tests=BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201108/247 X-Sequence-Number: 44694 This is a multi-part message in MIME format. --------------030203020608070305090407 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 08/22/2011 12:48 PM, Midge Brown wrote: > I was pushed to put the new version into production over the weekend, > which at least may provide me with some accurate feedback, and so will > see what happens for a bit before addressing the disk/drive layout. The good news is that deploying onto the split up configuration will give you lots of data to collect about just how the load is split up over the various parts of the database. You can just monitor which drives the I/O goes to. If there are some that are really underused, and can arrange downtime and disk space to merge them together in the future, that may be an option for improving performance one day. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us --------------030203020608070305090407 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 08/22/2011 12:48 PM, Midge Brown wrote:
 
I was pushed to put the new version into production over the weekend, which at least may provide me with some accurate feedback, and so will see what happens for a bit before addressing the disk/drive layout.

The good news is that deploying onto the split up configuration will give you lots of data to collect about just how the load is split up over the various parts of the database.  You can just monitor which drives the I/O goes to.  If there are some that are really underused,  and can arrange downtime and disk space to merge them together in the future, that may be an option for improving performance one day.

-- 
Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support  www.2ndQuadrant.us
--------------030203020608070305090407--