| From: | Shammat <shammat(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Poor performance after restoring database from snapshot on AWS RDS |
| Date: | 2024-06-05 08:31:04 |
| Message-ID: | d9ac68cc-3794-4c5d-8e60-1548647608ab@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Sam Kidman schrieb am 03.06.2024 um 10:06:
> We get very poor performance in the staging environment after this
> restore takes place - after some usage it seems to get better perhaps
> because of caching.
>
> The staging RDS instance is a smaller size than production (it has
> 32GB ram and 8 vCPU vs production's 128GB ram and 32 vCPU) but the
> performance seems to much worse than this decrease in resources would
> account for.
>
> I have seen some advice that vacuum analyze should be run after the
> snapshot restore but I thought this was supposed to happen
> automatically. If we did run it manually how would that help?
autovacuum will kick in eventually - but only after some time (which
is what you are seeing).
In general after a bulk load (e.g. restore of a backup or importing
data in any other way) running vacuum to udpate statistics is highly
recommended
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Durumdara | 2024-06-05 08:34:54 | Variant (Untyped) parameter for function/procedure |
| Previous Message | Radu Radutiu | 2024-06-05 08:16:49 | Re: Postgresql 16.3 Out Of Memory |