Re: Occasional giant spikes in CPU load

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Craig James" <craig_james(at)emolecules(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Occasional giant spikes in CPU load
Date: 2010-06-25 16:41:11
Message-ID: 4C2495D70200002500032B16@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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.

-Kevin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Kevin Grittner 2010-06-25 16:41:51 Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)
Previous Message Tom Molesworth 2010-06-25 16:39:05 Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)