public inbox for [email protected]  

help / color / mirror / Atom feed

From: Shammat <[email protected]>
To: [email protected]
Subject: Re: Poor performance after restoring database from snapshot on AWS RDS
Date: Wed, 5 Jun 2024 10:31:04 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+FDo=uz3+5vbQZDXN5SBAiZMnR0_w7YRZW+FS-VVuD3_XwB2g@mail.gmail.com>
References: <CA+FDo=uz3+5vbQZDXN5SBAiZMnR0_w7YRZW+FS-VVuD3_XwB2g@mail.gmail.com>


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

view thread (2+ messages)

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: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Poor performance after restoring database from snapshot on AWS RDS
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox