Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 46D39B5DBD6 for ; Wed, 17 Aug 2011 11:29:08 -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 10036-01 for ; Wed, 17 Aug 2011 14:28:57 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by mail.postgresql.org (Postfix) with ESMTP id BCD9EB5DBC4 for ; Wed, 17 Aug 2011 11:28:57 -0300 (ADT) Received: from [192.168.1.108] (unknown [173.165.13.38]) by smtp.mxes.net (Postfix) with ESMTPA id 34B5B22E253; Wed, 17 Aug 2011 10:28:56 -0400 (EDT) Subject: Re: Tuning Tips for a new Server Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Ogden In-Reply-To: <4E4BC51A.2080503@squeakycode.net> Date: Wed, 17 Aug 2011 09:28:56 -0500 Cc: pgsql-performance@postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <959BD2FA-0312-458B-BD5F-ED358D2C47ED@darkstatic.com> <4E4BC51A.2080503@squeakycode.net> To: Andy Colson X-Mailer: Apple Mail (2.1082) 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 X-Spam-Level: X-Archive-Number: 201108/174 X-Sequence-Number: 44621 On Aug 17, 2011, at 8:41 AM, Andy Colson wrote: > On 8/16/2011 8:35 PM, Ogden wrote: >> Hope all is well. I have received tremendous help from this list = prior and therefore wanted some more advice. >>=20 >> I bought some new servers and instead of RAID 5 (which I think = greatly hindered our writing performance), I configured 6 SCSI 15K = drives with RAID 10. This is dedicated to /var/lib/pgsql. The main OS = has 2 SCSI 15K drives on a different virtual disk and also Raid 10, a = total of 146Gb. I was thinking of putting Postgres' xlog directory on = the OS virtual drive. Does this even make sense to do? >>=20 >> The system memory is 64GB and the CPUs are dual Intel E5645 chips = (they are 6-core each). >>=20 >> It is a dedicated PostgreSQL box and needs to support heavy read and = moderately heavy writes. >>=20 >> Currently, I have this for the current system which as 16Gb Ram: >>=20 >> max_connections =3D 350 >>=20 >> work_mem =3D 32MB >> maintenance_work_mem =3D 512MB >> wal_buffers =3D 640kB >>=20 >> # This is what I was helped with before and made reporting queries = blaze by >> seq_page_cost =3D 1.0 >> random_page_cost =3D 3.0 >> cpu_tuple_cost =3D 0.5 >> effective_cache_size =3D 8192MB >>=20 >> Any help and input is greatly appreciated. >>=20 >> Thank you >>=20 >> Ogden >=20 > What seems to be the problem? I mean, if nothing is broke, then don't = fix it :-) >=20 > You say reporting query's are fast, and the disk's should take care of = your slow write problem from before. (Did you test the write = performance?) So, whats wrong? I was wondering what the best parameters would be with my new setup. = The work_mem obviously will increase as will everything else as it's a = 64Gb machine as opposed to a 16Gb machine. The configuration I posted = was for a 16Gb machine but this new one is 64Gb. I needed help in how to = jump these numbers up.=20 Thank you Ogden=