Hi Ken/ Will
I have checked the ulimit value and we are nowhere hitting the max 4096 that we have currently set. Is there any
otherexplanation why we should be thinking of bumping it to like ulimit -n 50000 ( Add ulimit -n 50000 to the start of
whateveryou use to start pgbouncer (init script, etc..)) even though we are not reaching 4096 max value
Regards
Prabhjot Singh
-----Original Message-----
From: ktm@rice.edu [mailto:ktm@rice.edu]
Sent: Thursday, June 18, 2015 11:10 AM
To: Sheena, Prabhjot
Cc: pgsql-performance@postgresql.org; pgsql-general@postgresql.org
Subject: Re: [PERFORM] PGBOUNCER ISSUE PLEASE HELP(Slowing down the site)
On Thu, Jun 18, 2015 at 05:41:01PM +0000, Sheena, Prabhjot wrote:
> Here is the output of OS limits
>
> postgres@symds-pg:~ $ ulimit -a
>
> core file size (blocks, -c) 0
> data seg size (kbytes, -d) unlimited
> scheduling priority (-e) 0
> file size (blocks, -f) unlimited
> pending signals (-i) 790527
> max locked memory (kbytes, -l) 32
> max memory size (kbytes, -m) unlimited
> open files (-n) 4096
> pipe size (512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority (-r) 0
> stack size (kbytes, -s) 10240
> cpu time (seconds, -t) unlimited
> max user processes (-u) 16384
> virtual memory (kbytes, -v) unlimited
> file locks (-x) unlimited
>
>
> Thanks
> Prabhjot
>
I would bump your open files as was suggested in your pgbouncer start script.
Regards,
Ken
