pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Geoffrey <lists@serioustechnology.com>
To: pgsql-admin@postgresql.org
Subject: problems after migration to new hardware
Date: Thu, 05 Apr 2007 14:18:03 -0400
Message-ID: <46153D5B.5020001@serioustechnology.com> (raw)

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



Message-ID: <46153D5B.5020001@serioustechnology.com>
Permalink:  ../46153D5B.5020001@serioustechnology.com/
Also on:    postgresql.org/message-id/46153D5B.5020001@serioustechnology.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: lists@serioustechnology.com
  Subject: Re: problems after migration to new hardware
  In-Reply-To: <46153D5B.5020001@serioustechnology.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox