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.