From: Chris Cheston <ccheston@gmail.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: postgres 7.4 at 100%
Date: Tue, 29 Jun 2004 01:00:10 -0700
Message-ID: <e071108e0406290100338c171d@mail.gmail.com> (raw)
In-Reply-To: <200406280947.59420.josh@agliodbs.com>
References: <e071108e04062423591d2b8aa9@mail.gmail.com>
<1088397641.1105.10.camel@localhost>
<17884.1088399982@sss.pgh.pa.us>
<200406280947.59420.josh@agliodbs.com>
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 <josh@agliodbs.com> 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
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ccheston@gmail.com, josh@agliodbs.com
Subject: Re: postgres 7.4 at 100%
In-Reply-To: <e071108e0406290100338c171d@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox