Re: Per thread Connection memory

From: Ankur Kaushik <ankurkaushik(at)gmail(dot)com>
To: jsoler(at)hoplasoftware(dot)com
Cc: Thorsten Schöning <tschoening(at)am-soft(dot)de>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Per thread Connection memory
Date: 2016-02-08 10:01:53
Message-ID: CALXoLqzz2_8_+rJg6D=Rd1nZohW9hX5ALqpzkbsQNngjN0=8SQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Given Tomcat setting works ,,,, Thanks

On Mon, Feb 1, 2016 at 4:53 PM, jaime soler gómez <jsoler(at)hoplasoftware(dot)com>
wrote:

> El vie, 29-01-2016 a las 14:18 +0100, Thorsten Schöning escribió:
> > 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.
>
> +1. If you don't want to keep many connections open in idle state, you
> can configure them at pgbouncer level or pool configuration in tomcat
> or application level.
>
> >
> >
> > > 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.
>
> Java is consuming 7/8 core of cpu, so i think you your look closer into
> tomcat and java processes.
>
> How about your work_mem parameter and top stats relatives of postgresql
> server ?
>
>
> >
> > 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.
>
> +1
>
> >
> > 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
> >
> >
> >
> --
> Jaime Soler Gómez
> HOPLA Software
> EnterpriseDB exclusive distributor ES/PT/IT & LatAm
> | P : (+34) 616 71 44 41 | SKYPE : jaimesolergomez | W :
> http://www.hoplasoftware.com/
>
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Andres Freund 2016-02-08 14:24:29 Re: 9.5 new setting "cluster name" and logging
Previous Message Stephen Frost 2016-02-07 03:00:37 Re: Setting up streaming replication with new server as master?