Re: backend proccess memory accumulates

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sebastian Gabbert <pg(at)huehnerhose(dot)de>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: backend proccess memory accumulates
Date: 2018-11-22 16:26:31
Message-ID: 5455.1542903991@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Sebastian Gabbert <pg(at)huehnerhose(dot)de> writes:
> Postgres is running on a dedicated FreeBSD 11.2 server with 32GB of RAM, there is a second server in hot standby / wal replication. My “worker” processes, mainly php processes, connect through pgbouncer (session mode).

> What I observed is that there are, at any time, around 10-15 postgres backend processes on my main db server consuming around 4GB of memory (RES in glances) each. These processes keep this footprint until pgbouncer closes the connection.

That is, most likely, almost entirely shared space (shared buffers and so
on). Sorting out how much is shared and how much is actually per-process
memory can be tricky, because most Unix process monitoring tools aren't
very good about showing the difference. I don't use FreeBSD enough to be
sure how to tell the difference with its tools --- but you can't get
anywhere with diagnosing PG's true memory consumption until you've got a
handle on that.

It would be interesting to know what you've got shared_buffers set to
on this server, though.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Sebastian Gabbert 2018-11-22 17:31:41 Re: backend proccess memory accumulates
Previous Message Sebastian Gabbert 2018-11-22 15:15:28 backend proccess memory accumulates