X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 8D93552A82 for ; Fri, 8 Apr 2005 22:09:27 +0100 (BST) 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 42774-10 for ; Fri, 8 Apr 2005 21:09:18 +0000 (GMT) Received: from vms040pub.verizon.net (vms040pub.verizon.net [206.46.252.40]) by svr1.postgresql.org (Postfix) with ESMTP id 7FA2752A56 for ; Fri, 8 Apr 2005 22:09:17 +0100 (BST) Received: from jfradkin ([66.15.127.235]) by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2 HotFix 0.04 (built Dec 24 2004)) with ESMTPA id <0IEN00HJWC3JYFME@vms040.mailsrvcs.net> for pgsql-sql@postgresql.org; Fri, 08 Apr 2005 16:09:20 -0500 (CDT) Date: Fri, 08 Apr 2005 17:09:21 -0400 From: "Joel Fradkin" Subject: Re: getting count for a specific querry In-reply-to: <1112993454.20921.89.camel@state.g2switchworks.com> To: "'Scott Marlowe'" , "'Vivek Khera'" Cc: Message-id: <008001c53c7f$3c35a930$797ba8c0@jfradkin> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Outlook, Build 10.0.6626 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.273 tagged_above=0 required=5 tests=AWL X-Spam-Level: * X-Archive-Number: 200504/128 X-Sequence-Number: 21021 I turned off hyperthreading (I saw that on the list that it did not help on Linux). I am using a pretty lightweight windows box Optiplex with IDE 750-meg internal 2.4 mghz cpu. My desktop has 2 gig, so might not be bad idea to try it local (I have installed), but me thinks its not totally a hardware issue for us. Joel Fradkin Do you run your 2650s with hyperthreading on? I found that slowed mine down under load, but we never had more than a couple dozen users hitting the db at once, so we may well have had a different load profile than what you're seeing. ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster