X-Original-To: pgsql-php-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 69E8F9DCD21 for ; Mon, 5 Dec 2005 13:04:33 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 85780-02 for ; Mon, 5 Dec 2005 13:04:32 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from hosting.commandprompt.com (128.commandprompt.com [207.173.200.128]) by postgresql.org (Postfix) with ESMTP id 395CA9DCD1C for ; Mon, 5 Dec 2005 13:04:31 -0400 (AST) Received: from [192.168.1.101] (or-67-76-146-141.sta.sprint-hsd.net [67.76.146.141]) (authenticated bits=0) by hosting.commandprompt.com (8.13.4/8.13.4) with ESMTP id jB5Gw9UP010040; Mon, 5 Dec 2005 08:58:10 -0800 Message-ID: <43947323.4090802@commandprompt.com> Date: Mon, 05 Dec 2005 09:04:35 -0800 From: "Joshua D. Drake" User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: James Dey CC: pgsql-php@postgresql.org Subject: Re: 64 Bit / Swap Issue? References: <20051205051145.7B2B4F0CE0@svr2.postgresql.org> In-Reply-To: <20051205051145.7B2B4F0CE0@svr2.postgresql.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (hosting.commandprompt.com [192.168.1.101]); Mon, 05 Dec 2005 08:58:10 -0800 (PST) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200512/5 X-Sequence-Number: 3351 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