On 6/25/10 9:41 AM, Kevin Grittner wrote:
> Craig James<craig_james(at)emolecules(dot)com> wrote:
>> I always just assumed that lots of backends that would be harmless
>> if each one was doing very little.
> Even if each is doing very little, if a large number of them happen
> to make a request at the same time, you can have problems. This is
> exactly where a connection pool can massively improve both
> throughput and response time. If you can arrange it, you want a
> connection pool which will put a limit on active database
> transactions and queue requests to start a new transaction until one
> of the pending ones finishes.
No, that's doesn't seem to be the case. There is no external activity that triggers this huge spike in usage. It even happens to our backup server when only one of us is using it to do a single query. This problem seems to be triggered by Postgres itself, not by anything external.
Per Tom's suggestion, I think upgrading to 8.4.4 is the answer. I'll learn more when our new hardware comes into use with a shiny new 8.4.4 installation.
In response to
pgsql-performance by date
|Next:||From: Tom Lane||Date: 2010-06-25 17:01:31|
|Subject: Re: Occasional giant spikes in CPU load |
|Previous:||From: Greg Smith||Date: 2010-06-25 16:55:17|
|Subject: Re: Occasional giant spikes in CPU load|