public inbox for [email protected]  

help / color / mirror / Atom feed

From: Sam Kidman <[email protected]>
To: [email protected]
Subject: Poor performance after restoring database from snapshot on AWS RDS
Date: Mon, 3 Jun 2024 18:06:18 +1000
Message-ID: <CA+FDo=uz3+5vbQZDXN5SBAiZMnR0_w7YRZW+FS-VVuD3_XwB2g@mail.gmail.com> (raw)

We keep the staging environment of our application up to date with
respect to production data by creating a new RDS instance for the
staging environment and restoring the most recent production snapshot
into it.

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?

Are there any other tools in postgres we can use to figure out why it
might be so much slower?

Best

--

Sam Kidman

Web Developer

Melbourne

view thread (2+ messages)  latest in thread

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: <CA+FDo=uz3+5vbQZDXN5SBAiZMnR0_w7YRZW+FS-VVuD3_XwB2g@mail.gmail.com>

* 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