Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 1CDD99FB3FA for ; Thu, 5 Apr 2007 15:23:27 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 21907-03-2 for ; Thu, 5 Apr 2007 15:23:17 -0300 (ADT) X-Greylist: delayed 00:05:01.154055 by SQLgrey-1.7.4 Received: from mout.perfora.net (mout.perfora.net [217.160.230.40]) by postgresql.org (Postfix) with ESMTP id C688B9FB40A for ; Thu, 5 Apr 2007 15:23:17 -0300 (ADT) Received: from [66.23.211.34] (helo=[172.16.255.106]) by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis), id 0MKp2t-1HZWXG1yJF-0008TY; Thu, 05 Apr 2007 14:18:15 -0400 Message-ID: <46153D5B.5020001@serioustechnology.com> Date: Thu, 05 Apr 2007 14:18:03 -0400 From: Geoffrey User-Agent: Thunderbird 1.5.0.8 (X11/20061025) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: problems after migration to new hardware Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX180jeYS5tmr7gRocgTH2pmLxCYR1Yfw1ff1EOd yA5yJPFNw0jIZow/0V+EaqQ7Rf3vQQBRlXLSC/5uXVLWTrwjWV z+3cW16Hsfk/8BwHwAZPpMQ2AcQdD0gzBdjA36sblc= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/88 X-Sequence-Number: 25152 We moved our application to a new machine last night. It is a Dell PowerEdge 6950 2X Dual Core. AMD Opteron 8214 2.2Ghz. 8GB Memory. The machine is running Redhat AS 4 Upd 4 and Redhat Cluster Suite. The SAN is an EMC SAS connected via fibre. We are using Postgres 7.4.16. We have recently had some major hardware issues and replaced the hardware with brand new Dell equipment. We expected a major performance increase over the previous being the old equipment was nearly three years old I will try and explain how things are configured. We have 10 separate postmasters running 5 on each node. Each of the postmasters is a single instance of each database. Each database is separated by division and also we have them separate so we can restart an postmaster with needing to restart all databases My largest database is about 7 GB. And the others run anywhere from 100MB - 1.8GB. The other configuration was RHEL3 and Postgres 7.4.13 and Redhat Cluster Suite. The application seemed to run much faster on the older equipment. My thoughts on the issues are that I could be something with the OS tuning. Here is what my kernel.shmmax, kernel.shmall = 1073741824. Is there something else that I could tune in the OS. My max_connections=35 and shared buffers=8192 for my largest database. -- Until later, Geoffrey Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin