X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 4215BD1D26D for ; Thu, 12 Feb 2004 22:20:31 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 25566-09 for ; Thu, 12 Feb 2004 18:20:31 -0400 (AST) Received: from bramble.mmrd.com (unknown [65.217.53.66]) by svr1.postgresql.org (Postfix) with ESMTP id 6C2A7D1BB95 for ; Thu, 12 Feb 2004 18:20:28 -0400 (AST) Received: from thorn.mmrd.com (thorn.mmrd.com [172.25.10.100]) by bramble.mmrd.com (8.12.8/8.12.8) with ESMTP id i1CLl9cM026922 for ; Thu, 12 Feb 2004 16:47:09 -0500 Received: from gnvex001.mmrd.com (gnvex001.mmrd.com [192.168.3.55]) by thorn.mmrd.com (8.11.6/8.11.6) with ESMTP id i1CMKQl15686 for ; Thu, 12 Feb 2004 17:20:26 -0500 Received: from intergylinux (intergylinux.mmrd.com [172.25.4.92]) by gnvex001.mmrd.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id XT88FRHZ; Thu, 12 Feb 2004 17:20:23 -0500 From: Chris Ruprecht Organization: CDRBill To: pgsql-performance@postgresql.org Subject: Re: Disappointing performance in db migrated from MS SQL Server Date: Thu, 12 Feb 2004 17:19:27 -0500 User-Agent: KMail/1.5.1 References: <200402121905.i1CJ5XW13096@candle.pha.pa.us> In-Reply-To: <200402121905.i1CJ5XW13096@candle.pha.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402121719.27666.chris@ruprecht.org> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/150 X-Sequence-Number: 5674 Bruce, my bet is on the limited amount of shared memory. The setup as posted by Leon only shows 80 MB. On a 4 GB database, that's not all that much. Depending on what he's doing, this might be a bottleneck. I don't like the virtual memory strategy of Linux too much and would rather increase this to 1 - 2 GB for the Postgres DB - Specially since he's not running anything else on the machine and he has 4 GB to play with. On Thursday 12 February 2004 14:05, Bruce Momjian wrote: > Leon Out wrote: [snip] > > My only guess is that the tests are I/O bound and therefore the faster > CPU's aren't helping PostgreSQL.