public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jeremy Smith <[email protected]>
To: Sam Kidman <[email protected]>
Cc: [email protected]
Subject: Re: Poor performance after restoring database from snapshot on AWS RDS
Date: Wed, 5 Jun 2024 08:09:34 -0400
Message-ID: <CAM8SmLUMREu3MOSpfh58EoV9ysgWi8sFkbj_BnBJQjeJn3C+7Q@mail.gmail.com> (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>

On Wed, Jun 5, 2024 at 4:23 AM Sam Kidman <[email protected]> wrote:

> 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.
>

This is due to the way that RDS restores snapshots.

From the docs (https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_RestoreFromSnapshot.html):

You can use the restored DB instance as soon as its status is
available. The DB instance continues to load data in the background.
This is known as lazy loading.

If you access data that hasn't been loaded yet, the DB instance
immediately downloads the requested data from Amazon S3, and then
continues loading the rest of the data in the background.



  -Jeremy

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