Re: The black art of postgresql.conf tweaking

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Gaetano Mendola <mendola(at)bigfoot(dot)com>
Cc: Paul Serby <paul(dot)serby(at)clockltd(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: The black art of postgresql.conf tweaking
Date: 2004-08-06 23:18:40
Message-ID: 200408061618.40047.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Martin Foster 2004-08-06 23:18:49 Re: Performance Bottleneck
Previous Message Martin Foster 2004-08-06 22:58:31 Re: Performance Bottleneck