From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | square_bob(at)yahoo(dot)com |
Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: amazon aroura config - seriously overcommited defaults? (May be Off Topic) |
Date: | 2018-12-08 19:21:20 |
Message-ID: | CAFj8pRCiGiZDrxVkOMT7BujVxPMU6OKGDj5=7YzqkDy=ugXMbw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-performance |
so 8. 12. 2018 v 20:04 odesílatel Square Bob <square_bob(at)yahoo(dot)com> napsal:
> All;
>
>
> My apologies if this is off topic.
>
>
> Our company is moving to Aurora, In the past I would take care not to
> allow postgresql to over-commit memory beyond the actual memory on the
> server, which meant I would add the buffer pool + (work_mem *
> max_connections) + (maintenance_work_mem * autovacuum threads)
>
>
> However as I look at the aroura defaults they are all off the charts,
> for example, based on the calculations in the config (amazon doesn't
> make it easy, some settings are in pages, some are in kb, some are who
> knows what) I see the following settings as default in our aroura config:
>
>
> The instance size is db.r4.xlarge
>
>
> this instance size is listed as having 30.5GB of ram
>
>
> Here's the default settings:
>
>
> shared_buffers: {DBInstanceClassMemory/10922}
>
> which equates to 24GB
>
>
> work_mem: 64000 (kb)
>
> which equates to 65.5MB
>
>
> maintenance_work_mem: GREATEST({DBInstanceClassMemory/63963136*1024},65536)
>
> which equates to 4.2GB
>
>
> max_connections: LEAST({DBInstanceClassMemory/9531392},5000)
>
> which equates to 3,380
>
>
> According to my math (If I got it right) in a worst case scenario,
>
> if we maxed out max_connections, work_mem and maintenance_work_mem limits
>
> the db would request 247GB of memory
>
>
> Additionally amazon has set effective_cache_size =
> {DBInstanceClassMemory/10922}
>
> which equates to about 2.9MB (which given the other outlandish setting
> may be the only appropriate setting in the system)
>
>
>
> What the hell is amazon doing here? Am I missing the boat on tuning
> postgresql memory? Is amazon simply counting on the bet that users will
> never fully utilize an instance?
>
>
nobody knows what patches are used there. Max connections over 1000 are
not good idea for native Postgres. But maybe there are some patches - or
just mostly idle connections are expected.
Regards
Pavel
> Thanks in advance
>
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Bob Lunney | 2018-12-08 19:48:24 | Re: amazon aroura config - seriously overcommited defaults? (May be Off Topic) |
Previous Message | Square Bob | 2018-12-08 19:03:27 | Fwd: amazon aroura config - seriously overcommited defaults? (May be Off Topic) |
From | Date | Subject | |
---|---|---|---|
Next Message | Bob Lunney | 2018-12-08 19:48:24 | Re: amazon aroura config - seriously overcommited defaults? (May be Off Topic) |
Previous Message | Square Bob | 2018-12-08 19:03:27 | Fwd: amazon aroura config - seriously overcommited defaults? (May be Off Topic) |