From james@mygus.com Mon Dec 5 08:20:38 2005 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 F03EE9DCD7A for ; Mon, 5 Dec 2005 04:20:38 -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 11997-06 for ; Mon, 5 Dec 2005 04:20:38 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svr2.postgresql.org (svr2.postgresql.org [65.19.161.25]) by postgresql.org (Postfix) with ESMTP id 46E9A9DCCA2 for ; Mon, 5 Dec 2005 04:20:34 -0400 (AST) Received: from mail-01.jhb.wbs.co.za (mail-01.jhb.wbs.co.za [196.30.31.196]) by svr2.postgresql.org (Postfix) with ESMTP id 7B2B4F0CE0 for ; Mon, 5 Dec 2005 05:11:45 +0000 (GMT) Received: from wbs-196-2-118-207.wbs.co.za ([196.2.118.207] helo=James) by mail-01.jhb.wbs.co.za with esmtp (Exim 4.50) id 1Ej8dK-0004f4-4G for pgsql-php@postgresql.org; Mon, 05 Dec 2005 07:11:33 +0200 From: "James Dey" To: Subject: 64 Bit / Swap Issue? Date: Mon, 5 Dec 2005 07:11:25 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0010_01C5F96B.1B5FFEA0" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcX5WkQ2BnERA2CrSlerWGvgFvXCiA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Original-Subject: 64 Bit / Swap Issue? Message-Id: <20051205051145.7B2B4F0CE0@svr2.postgresql.org> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=1.333 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.332] X-Spam-Score: 1.333 X-Spam-Level: * X-Archive-Number: 200512/1 X-Sequence-Number: 3348 This is a multi-part message in MIME format. ------=_NextPart_000_0010_01C5F96B.1B5FFEA0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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. I have been experiencing incredible slow performance from my server, and am at a loss for solution. Should I be moving back to a 32 bit system? This is the reply I have from Rackspace: "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." 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. Regards and thanks, James Dey james@mygus.com 0861-11-44-03 Intl. : +27 (0) 11 704-1945 Fax : +27 (0) 11 3888-907 Mobile : +27 (0) 82-7855-102 ------=_NextPart_000_0010_01C5F96B.1B5FFEA0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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.

 

I have been experiencing incredible slow performance from my server, and am at a = loss for solution. Should I be moving back to a 32 bit = system?

 

This is the = reply I have from Rackspace:

 

“Seco= ndly "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.”

 

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.

 

Regards and thanks,

 

James Dey

james@mygus.com=

 

0861-11-44-03

Intl. : +27 = (0) 11 704-1945

Fax : +27 (0) = 11 3888-907

Mobile : +27 (0) 82-7855-102

 

------=_NextPart_000_0010_01C5F96B.1B5FFEA0-- From desoi@pgedit.com Mon Dec 5 16:14:41 2005 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 534AE9DCB0A for ; Mon, 5 Dec 2005 12:14:41 -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 77150-09 for ; Mon, 5 Dec 2005 12:14:39 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svr2.postgresql.org (svr2.postgresql.org [65.19.161.25]) by postgresql.org (Postfix) with ESMTP id 658819DD610 for ; Mon, 5 Dec 2005 12:14:38 -0400 (AST) Received: from a2s5.a2hosting.com (host-209-124-50-10.a2webhosting.com [209.124.50.10]) by svr2.postgresql.org (Postfix) with ESMTP id 924A7F0B2F for ; Mon, 5 Dec 2005 16:14:37 +0000 (GMT) Received: from user-1120ji9.dsl.mindspring.com ([66.32.78.73] helo=[192.168.1.10]) by a2s5.a2hosting.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.52) id 1EjIz4-00007e-Dd; Mon, 05 Dec 2005 11:14:34 -0500 In-Reply-To: <20051205051145.7B2B4F0CE0@svr2.postgresql.org> References: <20051205051145.7B2B4F0CE0@svr2.postgresql.org> Mime-Version: 1.0 (Apple Message framework v733) Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed Message-Id: <682BE099-136C-44B1-8B9D-8A08FF0CA849@pgedit.com> Cc: pgsql-php@postgresql.org Content-Transfer-Encoding: quoted-printable From: John DeSoi Subject: Re: 64 Bit / Swap Issue? Date: Mon, 5 Dec 2005 11:14:30 -0500 To: James Dey X-Mailer: Apple Mail (2.733) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - a2s5.a2hosting.com X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - pgedit.com X-Source: X-Source-Args: X-Source-Dir: X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=1.332 required=5 tests=[RCVD_IN_BL_SPAMCOP_NET=1.332] X-Spam-Score: 1.332 X-Spam-Level: * X-Archive-Number: 200512/3 X-Sequence-Number: 3349 Hi James, On Dec 5, 2005, at 12:11 AM, James Dey wrote: > =93Secondly "sar" is showing that you are dipping quite a bit into =20 > your swap space. When dealing with a database server, any time =20 > that you move from RAM to swap you will see a massive performance =20 > drop, especially when dealing with as much swap as this machine =20 > has. At its peak you were hitting 70%(700M) of swap. Since =20 > PostgreSQL is unsupported I don't have any suggestions on query =20 > optimizations. However, at this point upgrading your available RAM =20= > would be one of my best suggestions.=94 > > > > Does anyone have any experience on this? Most of the things I have =20 > read suggest that I move back to 32 bit but I do think it=92s a step =20= > backward =96 that=92s if this can be supported. Welcome to the list. I don't have an answer for you but I'll suggest that you might have =20 better luck finding one on the performance list. Or even the general =20 list. Also there are archives for all lists which might also provide =20 some clues. John DeSoi, Ph.D. http://pgedit.com/ Power Tools for PostgreSQL From bruno@wolff.to Mon Dec 5 16:34:33 2005 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 5560D9DCD33 for ; Mon, 5 Dec 2005 12:34: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 79384-10 for ; Mon, 5 Dec 2005 12:34:32 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from wolff.to (wolff.to [66.93.197.194]) by postgresql.org (Postfix) with SMTP id 481089DCD43 for ; Mon, 5 Dec 2005 12:34:28 -0400 (AST) Received: (qmail 13671 invoked by uid 500); 5 Dec 2005 16:38:47 -0000 Date: Mon, 5 Dec 2005 10:38:47 -0600 From: Bruno Wolff III To: James Dey Cc: pgsql-php@postgresql.org Subject: Re: 64 Bit / Swap Issue? Message-ID: <20051205163847.GA12513@wolff.to> Mail-Followup-To: Bruno Wolff III , James Dey , pgsql-php@postgresql.org References: <20051205051145.7B2B4F0CE0@svr2.postgresql.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051205051145.7B2B4F0CE0@svr2.postgresql.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.069 required=5 tests=[AWL=0.069] X-Spam-Score: 0.069 X-Spam-Level: X-Archive-Number: 200512/4 X-Sequence-Number: 3350 On Mon, Dec 05, 2005 at 07:11:25 +0200, James Dey wrote: > > I have been experiencing incredible slow performance from my server, and am > at a loss for solution. Should I be moving back to a 32 bit system? I think it is unlikely that the switch to 64bit architecture is what is causing your problem. You should ask again on the performance list. You want to include some more details on hardware, such as the amount of memory and your disk set up. You should include your postgresql.conf settings as there might be something there that is causing a problem. You should state what version of postgres you are running and what OS you are using. You should include information about what else is running on that server. It is possible that something other than Postgres is using the memory. Have you looked at ps output to try to identify which processes are using lots of memory? If you have identified any slow queries, it would be helpful to see EXPLAIN ANALYSE output for them. Your problem is probably not a bad plan, but there could be an issue with a query taking up a lot of memory if you workmem limit is very high. From jd@commandprompt.com Mon Dec 5 17:04:33 2005 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