From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | "Anjan Dave" <adave(at)vantage(dot)com>, "Richard Huxton" <dev(at)archonet(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Tuning for mid-size server |
Date: | 2003-10-21 17:22:49 |
Message-ID: | 200310211022.49356.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Anjan,
> From what I know, there is a cache-row-set functionality that doesn't
> exist with the newer postgres...
What? PostgreSQL has always used the kernel cache for queries.
> Concurrent users will start from 1 to a high of 5000 or more, and could
> ramp up rapidly. So far, with increased users, we have gone up to
> starting the JVM (resin startup) with 1024megs min and max (recommended
> by Sun) - on the app side.
Well, just keep in mind when tuning that your calculations should be based on
*available* RAM, meaning RAM not used by Apache or the JVM.
With that many concurrent requests, you'll want to be *very* conservative with
sort_mem; I might stick to the default of 1024 if I were you, or even lower
it to 512k.
--
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | scott.marlowe | 2003-10-21 17:30:36 | Re: Tuning for mid-size server |
Previous Message | Josh Berkus | 2003-10-21 17:15:57 | Re: Tuning for mid-size server |