pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alex Balashov <abalashov@evaristesys.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Unexplained rapid growth in memory usage of idle backends
Date: Sat, 13 May 2023 19:49:58 -0400
Message-ID: <9844F4CE-A754-4C31-9CA0-EEF80EB6D747@evaristesys.com> (raw)
In-Reply-To: <1634073.1683942775@sss.pgh.pa.us>
References: <2D17E15D-8D5B-4DF7-A238-12455C2731D8@evaristesys.com>
	<1634073.1683942775@sss.pgh.pa.us>


> On May 12, 2023, at 9:52 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 
> Alex Balashov <abalashov@evaristesys.com> writes:
>> Occasionally, about once every 2 months, we'll get a slow-motion implosion over a period of about 24 hours, where the resident memory size of some of the backends shoots up from a reasonable few hundred MB to several gigs -- and will keep growing, e.g.
> 
> I'm a little suspicious that the excess memory consumption is a
> consequence of JIT-compiled code not getting recycled promptly.
> Do you have JIT enabled, and if so are you relying on it too much
> to turn it off?
> 
> I don't have any concrete idea of why JIT code management would work
> fine and then stop working fine, but we do have other reports of
> memory leaks from that.

Hi Tom, thanks for your response. JIT is enabled, but I'm not familiar with this feature and not sure what we are using which would touch JIT somehow. 

Also, am I wrong to imagine that a memory leak would leak memory gradually over time, rather than to be set off at some arbitrary point by the same exact workload that has been visited upon the database for the previous 1-2 months hitherto?

-- Alex

-- 
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800






view thread (9+ messages)  latest in thread

Message-ID: <9844F4CE-A754-4C31-9CA0-EEF80EB6D747@evaristesys.com>
Permalink:  ../9844F4CE-A754-4C31-9CA0-EEF80EB6D747@evaristesys.com/
Also on:    postgresql.org/message-id/9844F4CE-A754-4C31-9CA0-EEF80EB6D747@evaristesys.com

 · 

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-admin@postgresql.org
  Cc: abalashov@evaristesys.com, tgl@sss.pgh.pa.us, pgsql-admin@lists.postgresql.org
  Subject: Re: Unexplained rapid growth in memory usage of idle backends
  In-Reply-To: <9844F4CE-A754-4C31-9CA0-EEF80EB6D747@evaristesys.com>

* 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