From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Frank Knobbe <frank(at)knobbe(dot)us> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: postgres 7.4 at 100% |
Date: | 2004-06-28 22:47:38 |
Message-ID: | 200406281547.38742.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Frank,
> I understand tuning PG is almost an art form, yet it should be based on
> actual usage patterns, not just by system dimensions, don't you agree?
Well, it's both. It's more that available RAM determines your *upper* limit;
that is, on Linux, you don't really want to have more than 20% allocated to
the shared_buffers or you'll be taking memory away from the kernel.
Within that limit, data size, query complexity and volume, and whether or not
you have long-running procedures tell you whether you're at the low end or
the high end.
To futher complicate things, these calculations are all going to change with
7.5.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Harald Lau (Sector-X) | 2004-06-29 06:42:14 | no index-usage on aggregate-functions? |
Previous Message | Frank Knobbe | 2004-06-28 21:46:55 | Re: postgres 7.4 at 100% |