Received: from localhost (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id C1C69634419
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Sat, 21 Feb 2009 17:39:36 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 40388-06 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Sat, 21 Feb 2009 17:39:33 -0400 (AST)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from el-out-1112.google.com (el-out-1112.google.com
 [209.85.162.180])
	by mail.postgresql.org (Postfix) with ESMTP id ED2BA632E4F
	for <pgsql-admin@postgresql.org>; Sat, 21 Feb 2009 17:39:33 -0400 (AST)
Received: by el-out-1112.google.com with SMTP id y26so1006898ele.10
	for <pgsql-admin@postgresql.org>; Sat, 21 Feb 2009 13:39:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:in-reply-to:references
	:date:message-id:subject:from:to:cc:content-type
	:content-transfer-encoding;
	bh=s1pChIWHAsUiWXc3nH6iYGZBvN7Yx8ekqXoYT48s++E=;
	b=Xg88oHmFAA3OZmngW0c3CdxWBJ3BZtLovR8SVSWZj+rTdxc8EuCAW3m9aND+CWo5/c
	ivYUW5DrWxFjPVYrR4zMoswodPSjDtJa1d17aTYAyda0hhbKpmBwuN1iKF/8Au135kwo
	8LSItwdCvDi++p+IYaI7kfVDo0HB+vghIlXBM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	b=PcfY2IveCP1By+GvIZOUTEAsAGjsslhXCVsCmlz0dCJuMC91jvsXQoRT3sRY1M41or
	D9WwmihI2hw/2igzG9DqKz+GZp54OdsdiRKLs2iuJ+xnH34KneYvhyYsHfxob76xX/q7
	wqQigc5avOktOpFY7f+aQ5Gk3qiFWbELTl3cU=
MIME-Version: 1.0
Received: by 10.150.228.2 with SMTP id a2mr3524285ybh.155.1235252372484; Sat,
	21 Feb 2009 13:39:32 -0800 (PST)
In-Reply-To: <FE44E0D7EAD2ED4BB2165071DB8E328C0378F77A@egcrc-ex01.egcrc.org>
References: <FE44E0D7EAD2ED4BB2165071DB8E328C0378F760@egcrc-ex01.egcrc.org>
	<dcc563d10902192148s7f781086p1c0a469e0ebc1dc5@mail.gmail.com>
	<FE44E0D7EAD2ED4BB2165071DB8E328C0378F774@egcrc-ex01.egcrc.org>
	<200902202145.49391.uwe@oss4u.com>
	<dcc563d10902210057k329f93bat76d07ba0016a24fe@mail.gmail.com>
	<FE44E0D7EAD2ED4BB2165071DB8E328C0378F77A@egcrc-ex01.egcrc.org>
Date: Sat, 21 Feb 2009 14:39:32 -0700
Message-ID: <dcc563d10902211339g22e61e8dp914d0a21900b8ec6@mail.gmail.com>
Subject: Re: very, very slow performance
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Tena Sakai <tsakai@gallo.ucsf.edu>
Cc: "Uwe C. Schroeder" <uwe@oss4u.com>, pgsql-admin@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none
X-Spam-Level: 
X-Archive-Number: 200902/176
X-Sequence-Number: 31397

On Sat, Feb 21, 2009 at 3:11 AM, Tena Sakai <tsakai@gallo.ucsf.edu> wrote:
> Hi Scott,
>
> Thanks for clustering suggestion.  I have never used
> cluster command and I need to read up before I can
> use it.
>
> I have adjusted postgres parameters per your recommen-
> dation.  Work_mem is now 8GB, checkpoint_segments is
> raised to 100.  Shared_buffers is still at 1GB because
> this is bound by SHMMAX of kernal, which I cannot alter
> for maybe a few days.  I am thinking of setting SHMMAX
> to 8GB.

Yeah, I'd reverse those two and set work_mem to something in the 512M
range max.  keep in mind work_mem is per query / per sort.  4 queries
with3 sorts each = max allocation of work_mem*3*4...

 I may or may not be able to move up to 8.3.6

> over this weekend.  If not, sometime during the week.

definitely a good idea.