Re: Occasional giant spikes in CPU load - Mailing list pgsql-performance

From Kevin Grittner
Subject Re: Occasional giant spikes in CPU load
Date
Msg-id 4C2495D70200002500032B16@gw.wicourts.gov
Whole thread Raw
In response to Re: Occasional giant spikes in CPU load  (Craig James <craig_james@emolecules.com>)
Responses Re: Occasional giant spikes in CPU load  (Craig James <craig_james@emolecules.com>)
List pgsql-performance
Craig James <craig_james@emolecules.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.

-Kevin

pgsql-performance by date:

Previous
From: Tom Molesworth
Date:
Subject: Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)
Next
From: "Kevin Grittner"
Date:
Subject: Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)