From: | DHSC Webmaster <webmaster(at)dhs-club(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: performance issues |
Date: | 2001-06-14 14:49:44 |
Message-ID: | 3B28CF08.A038D9FE@dhs-club.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-sql |
Thank you Tom. That has seemed to help substantially.
I received another sugestion to increase -B 30000 which would give 240
meg. to postgres. I plan to give that a try. I've already reset the
SHMMAX val in sysctl to accomodate that size. Do you see any reason not
to try this? My thought is if some is good, more must be better. :)
Also I noticed in this artice:
http://www.ca.postgresql.org/docs/faq-english.html#3.7
mention of another memory parameter (-S), however the elephant book
refers to -S as silent mode.
Could you clarify this?
Tom Lane wrote:
>
> DHSC Webmaster <webmaster(at)dhs-club(dot)com> writes:
> > We are running 7.0.3 on a RH 7.0 box w/twin 733 pentium CPUs, 512 meg.
> > ram and a 3 drive raid 5 scsi array. The machine is dedicated. Our main
> > table is about 700,000 rows with an associated table of about 15,000
> > rows.
> > -N 128 -B 256
>
> That's not nearly enough buffers for an installation that size. Try -B
> of a few thousand.
>
> regards, tom lane
--
Bill MacArthur
Webmaster
DHS Club
From | Date | Subject | |
---|---|---|---|
Next Message | pgsql-admin | 2001-06-14 15:34:06 | 7.0.3 -> 7.1.2; pg_setlocale error |
Previous Message | brian | 2001-06-14 14:38:26 | vacuum error |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2001-06-14 14:52:08 | Re: search/replace in update |
Previous Message | Richard Huxton | 2001-06-14 12:02:52 | Re: Getting a specific row from a table |