On Fri, Jun 7, 2024 at 4:36 AM Sam Kidman wrote:
> > This is due to the way that RDS restores snapshots.
>
> Thanks, I never would have guessed. Would vacuum analyze be sufficient
> to defeat the lazy loading or would we need to do something more
> specific to our application? (for example. selec
> This is due to the way that RDS restores snapshots.
Thanks, I never would have guessed. Would vacuum analyze be sufficient
to defeat the lazy loading or would we need to do something more
specific to our application? (for example. select(*) on some commonly
used tables)
I think vacuum full woul
On Wed, Jun 5, 2024 at 4:23 AM Sam Kidman 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://doc
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 vCP
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
