X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 7164952A4D for ; Fri, 4 Mar 2005 18:30:11 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 47786-05 for ; Fri, 4 Mar 2005 18:30:10 +0000 (GMT) Received: from davinci.ethosmedia.com (server227.ethosmedia.com [209.128.84.227]) by svr1.postgresql.org (Postfix) with ESMTP id 1914652D45 for ; Fri, 4 Mar 2005 18:30:08 +0000 (GMT) X-EthosMedia-Virus-Scanned: no infections found Received: from [63.195.55.98] (account josh@agliodbs.com HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 7092290; Fri, 04 Mar 2005 10:31:58 -0800 From: Josh Berkus Organization: Aglio Database Solutions To: "Ken Egervari" Subject: Re: Help with tuning this query (with explain analyze finally) Date: Fri, 4 Mar 2005 10:29:11 -0800 User-Agent: KMail/1.6.2 Cc: References: <001001c51ef4$3849eeb0$6a01a8c0@KEN> <200503030935.14537.josh@agliodbs.com> <001d01c5204a$b440edf0$6a01a8c0@KEN> In-Reply-To: <001d01c5204a$b440edf0$6a01a8c0@KEN> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200503041029.11608.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.011 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/79 X-Sequence-Number: 10784 Ken, > I did everything you said and my query does perform a bit better. I've > been getting speeds from 203 to 219 to 234 milliseconds now. I tried > increasing the work mem and the effective cache size from the values you > provided, but I didn't see any more improvement. I've tried to looking > into setting the shared buffers for Windows XP, but I'm not sure how to do > it. I'm looking in the manual at: Now that you know how to change the shared_buffers, want to go ahead and run the query again? I'm pretty concerned about your case, because based on your description I would expect < 100ms on a Linux machine. So I'm wondering if this is a problem with WindowsXP performance, or if it's something we can fix through tuning. -- Josh Berkus Aglio Database Solutions San Francisco