AWS study finds PostgreSQL prewarming cuts restore delays
AWS compared Amazon RDS for PostgreSQL instances restored from the same snapshot. One 1,200-GiB database on gp3 was prewarmed with 15 parallel pg_prewarm sessions; another hydrated passively. The first instance completed storage initialization in about five hours.
Event / data period:
Published: · Updated:
AWS compared Amazon RDS for PostgreSQL instances restored from the same snapshot. One 1,200-GiB database on gp3 was prewarmed with 15 parallel pg_prewarm sessions; another hydrated passively. The first instance completed storage initialization in about five hours. Both instances used db.m5.4xlarge with gp3 storage configured at 20,000 IOPS and 600 MiB/s throughput.
The passive instance had reached only 23% after five hours, with completion estimated beyond 24 hours. In later tests, a large table scan took 44 seconds on the prewarmed instance and 571 on the other; a complex join took 123 and 1,531 seconds. AWS says results are specific to its test configuration.
Data
AWS study finds PostgreSQL prewarming cuts restore delays
AWS compared Amazon RDS for PostgreSQL instances restored from the same snapshot. One 1,200-GiB database on gp3 was prewarmed with 15 parallel pg_prewarm sessions; another hydrated passively. The first instance completed storage initialization in about five hours. Both instances used db.m5.4xlarge with gp3 storage configured at 20,000 IOPS and 600 MiB/s throughput. The passive instance had reached only 23% after five hours, with completion estimated beyond 24 hours. In later tests, a large table scan took 44 seconds on the prewarmed instance and 571 on the other; a complex join took 123 and 1,531 seconds. AWS says results are specific to its test configuration.
- · Occurred
AWS study finds PostgreSQL prewarming cuts restore delays
AWS compared Amazon RDS for PostgreSQL instances restored from the same snapshot. One 1,200-GiB database on gp3 was prewarmed with 15 parallel pg_prewarm sessions; another hydrated passively. The first instance completed storage initialization in about five hours. Both instances used db.m5.4xlarge with gp3 storage configured at 20,000 IOPS and 600 MiB/s throughput. The passive instance had reached only 23% after five hours, with completion estimated beyond 24 hours. In later tests, a large table scan took 44 seconds on the prewarmed instance and 571 on the other; a complex join took 123 and 1,531 seconds. AWS says results are specific to its test configuration.
Methodology
Reported values and benefits are attributed to the source; no independent measurement was made.
Updated:
Subjects and places
Subject proposals
- Science and technologySuggested
- Preserved editorial category/topic; broad candidate onlyaws.amazon.com ↗