Re: BUG #17269: Why is virtual memory usage of PostgreSQL growing constantly? - Mailing list pgsql-bugs

From Kyotaro Horiguchi
Subject Re: BUG #17269: Why is virtual memory usage of PostgreSQL growing constantly?
Date
Msg-id 20211108.100013.1114023989331664882.horikyota.ntt@gmail.com
Whole thread Raw
In response to Re: BUG #17269: Why is virtual memory usage of PostgreSQL growing constantly?  (菊池祐 <y.kikuchi0714@gmail.com>)
Responses Re: BUG #17269: Why is virtual memory usage of PostgreSQL growing constantly?
List pgsql-bugs
At Fri, 5 Nov 2021 18:15:01 +0900, 菊池祐 <y.kikuchi0714@gmail.com> wrote in 
> I attached postgresql.conf file.

> max_connections = 10000            # (change requires restart)

I think the moderate setting of max_connection is 100 to 200 or 300 on
a 128GB box. Depending on workload but it seems that you need to
reduce it to the same range.  1000 might be possible for super-light
weight workload but it is almost definite that 10000 don't fit 128GB
memory, or on CPUs with 16-32 cores.

I'm sure the clients are executing queries with quite low
frequency. Maybe you want to use connection pooler such like Pgpool-II
or pgbouncer, yandex/odyssey if the clients need to maintain their
connections to the server for a long time.

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: BUG #17245: Index corruption involving deduplicated entries
Next
From: Semab Tariq
Date:
Subject: Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data