Re: Poor performance after restoring database from snapshot on AWS RDS

Поиск
Список
Период
Сортировка
От Jeremy Smith
Тема Re: Poor performance after restoring database from snapshot on AWS RDS
Дата
Msg-id CAM8SmLUMREu3MOSpfh58EoV9ysgWi8sFkbj_BnBJQjeJn3C+7Q@mail.gmail.com
обсуждение исходный текст
Ответ на Poor performance after restoring database from snapshot on AWS RDS  (Sam Kidman <sam@fresho.com>)
Ответы Re: Poor performance after restoring database from snapshot on AWS RDS
Список pgsql-general
On Wed, Jun 5, 2024 at 4:23 AM Sam Kidman <sam@fresho.com> 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



В списке pgsql-general по дате отправления:

Предыдущее
От: Laurenz Albe
Дата:
Сообщение: Re: Logical replication type- WAL recovery fails and changes the size of wal segment in archivedir
Следующее
От: Gavin Roy
Дата:
Сообщение: Re: Purpose of pg_dump tar archive format?