pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: James Dey <james@mygus.com>
Cc: pgsql-php@postgresql.org
Subject: Re: 64 Bit / Swap Issue?
Date: Mon, 05 Dec 2005 09:04:35 -0800
Message-ID: <43947323.4090802@commandprompt.com> (raw)
In-Reply-To: <20051205051145.7B2B4F0CE0@svr2.postgresql.org>
References: <20051205051145.7B2B4F0CE0@svr2.postgresql.org>

James Dey wrote:
> -->
>
> Hi Guys,
>
> We have been running our systems on high end Redhat ES 32 Bit servers 
> without any sort of glitch. We have now set up a 64 bit Athlon server 
> running Redhat ES, installed the Redhat PgSQL as well as the PHP5 RPM.
>
Do the machines have a different amount of RAM? There is no reason that 
a 32 bit machine versus a 64bit machines should swap noticeably more 
unless something has changed.

> /“Secondly "sar" is showing that you are dipping quite a bit into your 
> swap space. When dealing with a database server, any time that you 
> move from RAM to swap you will see a massive performance drop, 
> especially when dealing with as much swap as this machine has. At its 
> peak you were hitting 70%(700M) of swap. Since PostgreSQL is 
> unsupported I don't have any suggestions on query optimizations. 
> However, at this point upgrading your available RAM would be one of my 
> best suggestions.”/
>
Well there response is correct but the question is why are you hitting 
swap. Please see my quseton above.
>
> Does anyone have any experience on this? Most of the things I have 
> read suggest that I move back to 32 bit but I do think it’s a step 
> backward – that’s if this can be supported.
>

There is no reason for you to move back to 32bit.

Joshua D. Drake




view thread (4+ messages)

Message-ID: <43947323.4090802@commandprompt.com>
Permalink:  ../43947323.4090802@commandprompt.com/
Also on:    postgresql.org/message-id/43947323.4090802@commandprompt.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: jd@commandprompt.com, james@mygus.com
  Subject: Re: 64 Bit / Swap Issue?
  In-Reply-To: <43947323.4090802@commandprompt.com>
  References: <20051205051145.7B2B4F0CE0@svr2.postgresql.org> <43947323.4090802@commandprompt.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