Re: Per thread Connection memory

Guten Tag Ankur Kaushik,
am Freitag, 29. Januar 2016 um 13:16 schrieben Sie:

> To Kill idle connection in every 10 sec , But after 15 -30 Min top command show as below

Killing idle connections is completely pointless, because those are
kept open for performance reasons, pgbouncer is designed to keep
connections open and idle, so that applications use them faster. If
you want less idle connections, reduce the configuration for those in
pgbouncer, but in the end you defeat its purpose that way.

>   PID USER      PR  NI  VIRT  RES  SHR S     %CPU %MEM    TIME+ COMMAND
> 10454 root        20   0 7101m   2.4g  11m  S    751.3 15.4 84:47.60 java

You problem is obviously that you don't have any clue what your
problem is, therefore you're just guessing things around. Don't do
that, at least look at the logs of your Tomcat, you may even use Java
Mission Control to monitor the performance of Tomcat and so on. This
high load might even be the result of your script introducing some
kind of a race condition, where you kill a connection just in that
moment where it was given to a using process in Tomcat.

If your problem is with Tomcat consuming too much memory or having
unexplainable high CPU load, don't waste your time with advancing the
complexity of your setup by installing pgbouncer. Focus on Tomcat and
its logs first.

Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning E-Mail: Thorsten(dot)Schoening(at)AM-SoFT(dot)de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/

Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow