Docker databases do not perform well under heavy load.
Everything can be configured to improve performance but going through the
Docker disk access layer will significantly decrease performance.
On Wednesday, November 20, 2024 at 06:06:36 AM GMT-5, Koen De Groote
wrote:
That explains a lot.
That explains a lot.
I have the default of 2 max_parallel_maintenance_workers set, should I set
this to 0?
I realize this is of course an improvement, but working with docker
containers, I'd like to avoid taking /dev/shm away from regular queries.
I assume setting max_parallel_maintenance_worker
Hello all,
Assume a machine with 16 CPU cores and 64GB of RAM. 300 max connections.
Postgres is running here, inside a docker container. Docker containers
receive a small amount of shared memory from /dev/shm
Experience teaches that the default 64MB of /dev/shm for the postgres
container, is not
On Wed, Nov 20, 2024 at 11:22 AM Koen De Groote wrote:
> Why would that be? It's the exact same data. The install is about 50GB in
> size. Is there something wrong with postgres 16, or did some settings
> significantly change, that I need to know about? I went over all the
> changelogs, nothing
