X-Original-To: pgsql-performance-postgresql.org@postgresql.org
Received: from localhost (mx1.hub.org [200.46.208.251])
	by postgresql.org (Postfix) with ESMTP id 4793D9FB1D7
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Thu, 14 Sep 2006 19:24:48 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024)
	with ESMTP id 93334-10 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Thu, 14 Sep 2006 19:24:30 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-
Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.232])
	by postgresql.org (Postfix) with ESMTP id 910A99FA2B9
	for <pgsql-performance@postgresql.org>;
	Thu, 14 Sep 2006 19:24:44 -0300 (ADT)
Received: by wx-out-0506.google.com with SMTP id t13so2997547wxc
	for <pgsql-performance@postgresql.org>;
	Thu, 14 Sep 2006 15:24:43 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=IMSW0iUcqQD9bmQ36hu4DDpSbddkV8YVe/x+GQw1TbwdU4un/gP0Pom9Du6kOtD9sAl0ct/Hcu+Q9aaAus1FQBKEhGP/d/n3mYMLgNV2gTBkdD2Bloa/peLs5YdxdCBsr9PfrYt25kPnyvjV2SZDYaAPIW0Cmn3Sb32cFtRRV6g=
Received: by 10.90.113.18 with SMTP id l18mr3534630agc;
	Thu, 14 Sep 2006 15:24:43 -0700 (PDT)
Received: by 10.90.36.2 with HTTP; Thu, 14 Sep 2006 15:24:43 -0700 (PDT)
Message-ID: <1d4e0c10609141524j3532e140i308111908c1ab437@mail.gmail.com>
Date: Fri, 15 Sep 2006 00:24:43 +0200
From: "Guillaume Smet" <guillaume.smet@gmail.com>
To: "=?ISO-8859-1?Q?J=E9r=F4me_BENOIS?=" <benois@argia-engineering.fr>
Subject: Re: High CPU Load
Cc: "Scott Marlowe" <smarlowe@g2switchworks.com>,
	"Dave Dutcher" <dave@tridecap.com>, pgsql-performance@postgresql.org,
	"Xavier Milliard" <milliard@argia.fr>
In-Reply-To: <1158270523.5167.18.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <004001c6d80e$bdef5bc0$8300a8c0@tridecap.com>
	<1158249411.24726.17.camel@state.g2switchworks.com>
	<1158268058.5167.2.camel@localhost.localdomain>
	<1d4e0c10609141422o57ecf28eobf3d0b7594bb242f@mail.gmail.com>
	<1158270523.5167.18.camel@localhost.localdomain>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.288 tagged_above=0 required=5 tests=AWL,
	DNS_FROM_RFC_ABUSE, SPF_PASS
X-Spam-Level: 
X-Archive-Number: 200609/181
X-Sequence-Number: 20867

On 9/14/06, J=E9r=F4me BENOIS <benois@argia-engineering.fr> wrote:
> Yes i have a lot of users ;-)

So your work_mem is probably far too high (that's what I told you in
my first message) and you probably swap when you have too many users.
Remember that work_mem can be used several times per query (and it's
especially the case when you have a lot of sorts).
When your load is high, check your swap activity and your io/wait. top
gives you these information. If you swap, lower your work_mem to 32 MB
for example then see if it's enough for your queries to run fast (you
can check if there are files created in the $PGDATA/base/<your
database oid>/pg_tmp) and if it doesn't swap. Retry with a
lower/higher value to find the one that fits best to your queries and
load.

> I agree but by moment DB Server is so slow.

Yep, that's the information that was missing :).

> what's means "HT" please ?

Hyper threading. It's usually not recommended to enable it on
PostgreSQL servers. On most servers, you can disable it directly in
the BIOS.

--
Guillaume