From: Josh Berkus <josh@agliodbs.com>
To: Anjan Dave <adave@vantage.com>
To: Richard Huxton <dev@archonet.com>
To: pgsql-performance@postgresql.org
Subject: Re: Tuning for mid-size server
Date: Tue, 21 Oct 2003 10:22:49 -0700
Message-ID: <200310211022.49356.josh@agliodbs.com> (raw)
In-Reply-To: <2F2E24372F10744588A27DEECC85FE04D27FBF@vt-pe2550-001.vantage.vantage.com>
References: <2F2E24372F10744588A27DEECC85FE04D27FBF@vt-pe2550-001.vantage.vantage.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, adave@vantage.com, dev@archonet.com
Subject: Re: Tuning for mid-size server
In-Reply-To: <200310211022.49356.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox