Skip site navigation (1) Skip section navigation (2)

Re: Server hitting 100% CPU usage, system comes to a crawl.

From: Radosław Smogura <rsmogura(at)softperience(dot)eu>
To: John R Pierce <pierce(at)hogranch(dot)com>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Server hitting 100% CPU usage, system comes to a crawl.
Date: 2011-10-28 07:53:57
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-general
On Thu, 27 Oct 2011 12:43:00 -0700, John R Pierce wrote:
> On 10/27/11 11:39 AM, Brian Fehrle wrote:
>> I've got a system that has 32 cores and 128 gigs of ram. We have 
>> connection pooling set up, with about 100 - 200 persistent connections 
>> open to the database. Our applications then use these connections to 
>> query the database constantly, but when a connection isn't currently 
>> executing a query, it's <IDLE>. On average, at any given time, there 
>> are 3 - 6 connections that are actually executing a query, while the 
>> rest are <IDLE>.
> thats not a very effective use of pooling.   the pooling model, you'd
> have a connection pool sufficient actual database connections to
> satisfy your concurrency requirements, and your apps would grab a
> connection from the pool, do a transaction, then release the
> connection back to the pool.
> now, I don't know that this has anything to do with your performance
> problem, I'm just pointing out this anomaly.  a pool doesn't do much
> good if the clients grab a connection and just sit on it.
> --
> john r pierce                            N 37, W 122
> santa cruz ca                         mid-left coast
It is good model, he have 3-6 connection at one time, so it's look 
quite clear that icrease of concurrent connections is caused by 
unexpected background processing.

In response to

pgsql-general by date

Next:From: Gregg JaskiewiczDate: 2011-10-28 07:58:26
Subject: Re: [PERFORM] Performance Problem with postgresql 9.03, 8GB RAM,Quadcore Processor Server--Need help!!!!!!!
Previous:From: Thomas KellererDate: 2011-10-28 07:29:49
Subject: "Named" column default expression

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group