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 BA2AED1B1B6 for ; Tue, 29 Jun 2004 05:00:15 -0300 (ADT) 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 86483-02 for ; Tue, 29 Jun 2004 08:00:13 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.241]) by svr1.postgresql.org (Postfix) with SMTP id CFA78D1B1EC for ; Tue, 29 Jun 2004 05:00:09 -0300 (ADT) Received: by mproxy.gmail.com with SMTP id q44so599570cwc for ; Tue, 29 Jun 2004 01:00:11 -0700 (PDT) Received: by 10.38.79.48 with SMTP id c48mr99042rnb; Tue, 29 Jun 2004 01:00:10 -0700 (PDT) Message-ID: Date: Tue, 29 Jun 2004 01:00:10 -0700 From: Chris Cheston To: Josh Berkus Subject: Re: postgres 7.4 at 100% Cc: pgsql-performance@postgresql.org In-Reply-To: <200406280947.59420.josh@agliodbs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <1088397641.1105.10.camel@localhost> <17884.1088399982@sss.pgh.pa.us> <200406280947.59420.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/284 X-Sequence-Number: 7342 Wow, this simple query is taking 676.24 ms to execute! it only takes 18 ms on our other machine. This table has 150,000 rows. Is this normal? no, the machine is not running software RAID. Anyone have any ideas next as to what I should do to debug this? I'm really wondering if the Linux OS running SMP is the cause. Thanks, Chris live=# explain analyze SELECT id FROM calllogs WHERE from = 'you'; QUERY PLAN ---------------------------------------------------------------------------------------------------------- Seq Scan on calllogs (cost=0.00..136.11 rows=24 width=4) (actual time=0.30..574.72 rows=143485 loops=1) Filter: (from = 'you'::character varying) Total runtime: 676.24 msec (3 rows) explain analyze for inserts is fast too. On Mon, 28 Jun 2004 09:47:59 -0700, Josh Berkus wrote: > > Tom, > > > So while he surely should not go back to 40, it seems there's another > > factor involved here that we've not recognized yet. > > I'd agree. Actually, the first thing I'd do, were it my machine, is reboot it > and run memtest86 overnight. CPU thrashing like that may indicate bad RAM. > > If the RAM checks out, I'd like to see the EXPLAIN ANALYZE for some of the > longest-running queries, and for those INSERTS. > > Also, is the new machine running Software RAID? > > -- > Josh Berkus > Aglio Database Solutions > San Francisco > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org >