From: Josh Berkus <josh@agliodbs.com>
To: Gaetano Mendola <mendola@bigfoot.com>
Cc: Paul Serby <paul.serby@clockltd.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: The black art of postgresql.conf tweaking
Date: Fri, 6 Aug 2004 16:18:40 -0700
Message-ID: <200408061618.40047.josh@agliodbs.com> (raw)
In-Reply-To: <4113CD75.2060508@bigfoot.com>
References: <4110DA83.7020505@clockltd.com>
<200408060929.19840.josh@agliodbs.com>
<4113CD75.2060508@bigfoot.com>
Gaetano,
> Of course your are speaking about the "worst case", I aplly in scenarios
like
> this on the rule 80/20: 80% of connection will perform a sort and 20% will
allocate
> memory for the sort operation in the same window time:
Well, I suppose it depends on how aggresive your connection pooling is. If
you minimize idle connections, then 300 connections can mean 200 concurrent
queries. And since Paul *is* having problems, this is worth looking into.
--
-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, mendola@bigfoot.com, paul.serby@clockltd.com
Subject: Re: The black art of postgresql.conf tweaking
In-Reply-To: <200408061618.40047.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