pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: ktm@rice.edu <ktm@rice.edu>
To: Sheena, Prabhjot <Prabhjot.Singh@classmates.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Cc: pgsql-general@postgresql.org <pgsql-general@postgresql.org>
Subject: Re: [PERFORM] PGBOUNCER ISSUE PLEASE HELP(Slowing down the site)
Date: Thu, 18 Jun 2015 12:16:23 -0500
Message-ID: <20150618171623.GT31129@aart.rice.edu> (raw)
In-Reply-To: <13E39D789E19FF4E9A87F6D456F3F9820123C607@SEAMBX02.sea.corp.int.untd.com>
References: <13E39D789E19FF4E9A87F6D456F3F9820123C607@SEAMBX02.sea.corp.int.untd.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-general>

On Thu, Jun 18, 2015 at 05:09:10PM +0000, Sheena, Prabhjot wrote:
> Guys
>          I have an issue going on with PGBOUNCER which is slowing down the site
> 
> PGBOUNCER VERSION:  pgbouncer-1.5.4-2.el6 (Hosted on separate machine) (16 cpu) 98GB RAM
> DATABASE VERION:         postgresql 9.3
> 
> When the total client connections to pgbouncer are close to 1000, site application works fine but when  the total client connections crosses 1150 site application starts showing slowness.
> 
> Here is an example of output
> 
> postgres@symds-pg:~ $ netstat -atnp | grep 5432  | wc
> (Not all processes could be identified, non-owned process info
> will not be shown, you would have to be root to see it all.)
>     960    6720  104640
> 
> 
> As you can see total connections are like 960 right now my site application is working fine. When connections crosses 1150  and even though I see lot of available connections coz my  default_pool_size is set high to 250  but still the application gets slow. Database performance  on the other end is great with no slow running queries or anything. So the only place I can think the issue is at PGBOUNCER end.
> 

Hi Prabhjot,

This is classic behavior when you have a 1024 file limit. When you are below that
number, it work fine. Above that number, you must wait for a connection to close
and exit before you can connect which will cause a delay. See what ulimit has to
say?

Regards,
Ken


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



view thread (10+ messages)  latest in thread

Message-ID: <20150618171623.GT31129@aart.rice.edu>
Permalink:  ../20150618171623.GT31129@aart.rice.edu/
Also on:    postgresql.org/message-id/20150618171623.GT31129@aart.rice.edu

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: ktm@rice.edu, Prabhjot.Singh@classmates.com, pgsql-general@postgresql.org
  Subject: Re: [PERFORM] PGBOUNCER ISSUE PLEASE HELP(Slowing down the site)
  In-Reply-To: <20150618171623.GT31129@aart.rice.edu>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox