{"article":{"annotation":{"article_id":"aws-rds-postgresql-snapshot-restore-prewarming-test","available_at":"2026-10-15T21:30:31.110926Z","geography_revision":"ef6ee0010dda5fe7b240fd514749b43e214c57da73222d2e40ec83b276dd0977","id":"76ddc940bd8e7ab82402fc294afaa72557d2badf118c3b5177a67c27a68c6450","input_sha256":"c0713268f4014cd33e3531f2ad93f56e3d6150434101330af4733278689f9818","limitations":["Rule-derived subjects are candidates, not verified editorial labels or calibrated model probabilities.","Coverage is distinct from event location. Unknown country/city/coordinates remain absent; no automatic geocoding.","Article geometries keep their stated precision and methodology; reproducing them is not independent coordinate verification."],"method":"controlled-rules-v1","places":[],"rules_sha256":"fb5ad3c27c91cb840f7a0a05f7f64a5cb26ad0374409ff9457f277c7092e22b4","schema_version":1,"subjects":[{"concept_id":"medtop:13000000","confidence":null,"confidence_method":null,"evidence":[{"field":"category+topics","language":"en","note":"Preserved editorial category/topic; broad candidate only","source_urls":["https://aws.amazon.com/blogs/database/reducing-storage-initialization-impact-in-amazon-rds-for-postgresql-after-snapshot-restore/"]}],"method":"controlled-rules-v1","rule_id":"technology-broad","status":"candidate"}],"taxonomy_revision":"1f2db31d811fca07e99b16d402c10e2cc2965c9df1c7b41d9be348b40a24e7fb","taxonomy_version":"IPTC Media Topics 2026-Q2"},"api_url":"https://newsverum.com/api/v1/articles/aws-rds-postgresql-snapshot-restore-prewarming-test?lang=en","category":"technology","content":{"key_points":[],"paragraphs":["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."],"sections":[]},"corrections":[],"country":null,"data":{"blocks":[{"description":{"ar":"قارنت AWS مثيلات Amazon RDS for PostgreSQL مستعادة من اللقطة نفسها. جرى إعداد قاعدة بيانات بحجم 1,200 غيغابايت على gp3 مسبقاً باستخدام 15 جلسة pg_prewarm متوازية، بينما تُركت أخرى للتحميل التلقائي. واكتمل إعداد التخزين في الأولى خلال نحو خمس ساعات. واستخدم المثيلان db.m5.4xlarge مع تخزين gp3 مضبوطاً على 20,000 IOPS ومعدل نقل 600 MiB/s. لم يتجاوز المثيل السلبي 23% بعد خمس ساعات، وقدر اكتماله بأكثر من 24 ساعة. وفي الاختبارات اللاحقة، استغرق مسح جدول كبير 44 ثانية في المثيل المهيأ مسبقاً و571 في الآخر؛ واستغرق الربط المعقد 123 و1,531 ثانية. وتقول AWS إن النتائج تخص إعداد الاختبار المحدد.","de":"AWS verglich Amazon-RDS-for-PostgreSQL-Instanzen, die aus demselben Snapshot wiederhergestellt wurden. Eine 1.200-GiB-Datenbank auf gp3 wurde mit 15 parallelen pg_prewarm-Sitzungen vorgewärmt; eine andere hydratisierte passiv. Bei der ersten war die Speicherinitialisierung nach etwa fünf Stunden abgeschlossen. Beide Instanzen nutzten db.m5.4xlarge mit gp3-Speicher, konfiguriert auf 20.000 IOPS und 600 MiB/s Durchsatz. Die passive Instanz hatte nach fünf Stunden erst 23 Prozent erreicht; die Fertigstellung wurde auf mehr als 24 Stunden geschätzt. Danach dauerte ein großer Tabellenscan auf der vorgewärmten Instanz 44 statt 571 Sekunden, ein komplexer Join 123 statt 1.531 Sekunden. AWS betont, dass die Werte für den konkreten Testaufbau gelten.","en":"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.","es":"AWS comparó instancias de Amazon RDS for PostgreSQL restauradas desde la misma instantánea. Una base de 1.200 GiB en gp3 se precalentó con 15 sesiones pg_prewarm paralelas; otra se hidrató de forma pasiva. La inicialización del almacenamiento de la primera terminó en unas cinco horas. Ambas instancias usaron db.m5.4xlarge con almacenamiento gp3 configurado a 20.000 IOPS y 600 MiB/s de rendimiento. La instancia pasiva solo había alcanzado el 23% tras cinco horas y se estimó que tardaría más de 24 horas. Después, un escaneo de tabla grande tomó 44 segundos en la instancia precalentada y 571 en la otra; una unión compleja, 123 y 1.531 segundos. AWS dice que los resultados corresponden a esa configuración de prueba.","fr":"AWS a comparé des instances Amazon RDS for PostgreSQL restaurées depuis le même snapshot. Une base de 1 200 Gio sur gp3 a été préchauffée avec 15 sessions pg_prewarm parallèles; une autre s’est hydratée passivement. L’initialisation de la première s’est achevée en environ cinq heures. Les deux instances utilisaient db.m5.4xlarge avec un stockage gp3 configuré à 20 000 IOPS et un débit de 600 MiB/s. L’instance passive n’avait atteint que 23 % après cinq heures, avec une fin estimée au-delà de 24 heures. Ensuite, un balayage de grande table a pris 44 secondes sur l’instance préchauffée contre 571 sur l’autre; une jointure complexe, 123 et 1 531 secondes. AWS précise que ces résultats correspondent à sa configuration de test.","pt":"A AWS comparou instâncias do Amazon RDS for PostgreSQL restauradas do mesmo snapshot. Um banco de 1.200 GiB em gp3 foi pré-aquecido com 15 sessões pg_prewarm paralelas; outro hidratou passivamente. A inicialização do armazenamento na primeira foi concluída em cerca de cinco horas. Ambas as instâncias usaram db.m5.4xlarge com armazenamento gp3 configurado para 20.000 IOPS e vazão de 600 MiB/s. A instância passiva havia alcançado apenas 23% após cinco horas, com conclusão estimada acima de 24 horas. Depois, uma leitura de tabela grande levou 44 segundos na instância pré-aquecida e 571 na outra; uma junção complexa, 123 e 1.531 segundos. A AWS afirma que os resultados são específicos daquela configuração de teste.","tr":"AWS, aynı anlık görüntüden geri yüklenen Amazon RDS for PostgreSQL örneklerini karşılaştırdı. 1.200 GiB'lık gp3 veritabanına sahip örneklerden biri 15 paralel pg_prewarm oturumuyla ısıtıldı; diğeri pasif biçimde yüklendi. İlk örnekte depolama yaklaşık beş saatte tamamen hazırlandı. Karşılaştırılan iki örnek de 20.000 IOPS ve 600 MiB/s aktarım hızına ayarlı gp3 depolamada db.m5.4xlarge kullanıyordu. Pasif örnek beş saat sonra yalnızca yüzde 23'e ulaşmıştı; tamamlanması 24 saati aşacak şekilde tahmin edildi. Sonraki testte büyük tablo taraması önceden ısıtılan örnekte 44 saniye, diğerinde 571 saniye; karmaşık birleştirme 123 ve 1.531 saniye sürdü. AWS, sonuçların test yapılandırmasına özgü olduğunu belirtiyor."},"id":"source-report","items":[{"date":"2026-10-14","description":{"ar":"قارنت AWS مثيلات Amazon RDS for PostgreSQL مستعادة من اللقطة نفسها. جرى إعداد قاعدة بيانات بحجم 1,200 غيغابايت على gp3 مسبقاً باستخدام 15 جلسة pg_prewarm متوازية، بينما تُركت أخرى للتحميل التلقائي. واكتمل إعداد التخزين في الأولى خلال نحو خمس ساعات. واستخدم المثيلان db.m5.4xlarge مع تخزين gp3 مضبوطاً على 20,000 IOPS ومعدل نقل 600 MiB/s. لم يتجاوز المثيل السلبي 23% بعد خمس ساعات، وقدر اكتماله بأكثر من 24 ساعة. وفي الاختبارات اللاحقة، استغرق مسح جدول كبير 44 ثانية في المثيل المهيأ مسبقاً و571 في الآخر؛ واستغرق الربط المعقد 123 و1,531 ثانية. وتقول AWS إن النتائج تخص إعداد الاختبار المحدد.","de":"AWS verglich Amazon-RDS-for-PostgreSQL-Instanzen, die aus demselben Snapshot wiederhergestellt wurden. Eine 1.200-GiB-Datenbank auf gp3 wurde mit 15 parallelen pg_prewarm-Sitzungen vorgewärmt; eine andere hydratisierte passiv. Bei der ersten war die Speicherinitialisierung nach etwa fünf Stunden abgeschlossen. Beide Instanzen nutzten db.m5.4xlarge mit gp3-Speicher, konfiguriert auf 20.000 IOPS und 600 MiB/s Durchsatz. Die passive Instanz hatte nach fünf Stunden erst 23 Prozent erreicht; die Fertigstellung wurde auf mehr als 24 Stunden geschätzt. Danach dauerte ein großer Tabellenscan auf der vorgewärmten Instanz 44 statt 571 Sekunden, ein komplexer Join 123 statt 1.531 Sekunden. AWS betont, dass die Werte für den konkreten Testaufbau gelten.","en":"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.","es":"AWS comparó instancias de Amazon RDS for PostgreSQL restauradas desde la misma instantánea. Una base de 1.200 GiB en gp3 se precalentó con 15 sesiones pg_prewarm paralelas; otra se hidrató de forma pasiva. La inicialización del almacenamiento de la primera terminó en unas cinco horas. Ambas instancias usaron db.m5.4xlarge con almacenamiento gp3 configurado a 20.000 IOPS y 600 MiB/s de rendimiento. La instancia pasiva solo había alcanzado el 23% tras cinco horas y se estimó que tardaría más de 24 horas. Después, un escaneo de tabla grande tomó 44 segundos en la instancia precalentada y 571 en la otra; una unión compleja, 123 y 1.531 segundos. AWS dice que los resultados corresponden a esa configuración de prueba.","fr":"AWS a comparé des instances Amazon RDS for PostgreSQL restaurées depuis le même snapshot. Une base de 1 200 Gio sur gp3 a été préchauffée avec 15 sessions pg_prewarm parallèles; une autre s’est hydratée passivement. L’initialisation de la première s’est achevée en environ cinq heures. Les deux instances utilisaient db.m5.4xlarge avec un stockage gp3 configuré à 20 000 IOPS et un débit de 600 MiB/s. L’instance passive n’avait atteint que 23 % après cinq heures, avec une fin estimée au-delà de 24 heures. Ensuite, un balayage de grande table a pris 44 secondes sur l’instance préchauffée contre 571 sur l’autre; une jointure complexe, 123 et 1 531 secondes. AWS précise que ces résultats correspondent à sa configuration de test.","pt":"A AWS comparou instâncias do Amazon RDS for PostgreSQL restauradas do mesmo snapshot. Um banco de 1.200 GiB em gp3 foi pré-aquecido com 15 sessões pg_prewarm paralelas; outro hidratou passivamente. A inicialização do armazenamento na primeira foi concluída em cerca de cinco horas. Ambas as instâncias usaram db.m5.4xlarge com armazenamento gp3 configurado para 20.000 IOPS e vazão de 600 MiB/s. A instância passiva havia alcançado apenas 23% após cinco horas, com conclusão estimada acima de 24 horas. Depois, uma leitura de tabela grande levou 44 segundos na instância pré-aquecida e 571 na outra; uma junção complexa, 123 e 1.531 segundos. A AWS afirma que os resultados são específicos daquela configuração de teste.","tr":"AWS, aynı anlık görüntüden geri yüklenen Amazon RDS for PostgreSQL örneklerini karşılaştırdı. 1.200 GiB'lık gp3 veritabanına sahip örneklerden biri 15 paralel pg_prewarm oturumuyla ısıtıldı; diğeri pasif biçimde yüklendi. İlk örnekte depolama yaklaşık beş saatte tamamen hazırlandı. Karşılaştırılan iki örnek de 20.000 IOPS ve 600 MiB/s aktarım hızına ayarlı gp3 depolamada db.m5.4xlarge kullanıyordu. Pasif örnek beş saat sonra yalnızca yüzde 23'e ulaşmıştı; tamamlanması 24 saati aşacak şekilde tahmin edildi. Sonraki testte büyük tablo taraması önceden ısıtılan örnekte 44 saniye, diğerinde 571 saniye; karmaşık birleştirme 123 ve 1.531 saniye sürdü. AWS, sonuçların test yapılandırmasına özgü olduğunu belirtiyor."},"label":{"ar":"دراسة AWS: التهيئة المسبقة لـPostgreSQL تقلل تأخر الاستعادة","de":"AWS-Studie: PostgreSQL-Vorwärmung verkürzt Wiederherstellungszeiten","en":"AWS study finds PostgreSQL prewarming cuts restore delays","es":"Estudio de AWS: el precalentamiento reduce demoras de restauración","fr":"Une étude AWS montre que le préchauffage réduit les délais de restauration","pt":"Estudo da AWS aponta que pré-aquecimento reduz atrasos na restauração","tr":"AWS çalışması: PostgreSQL ön ısıtması geri yükleme gecikmesini azalttı"},"status":"occurred"}],"methodology":{"ar":"تُنسب القيم والمنافع إلى المصدر؛ ولم يُجرَ قياس مستقل.","de":"Werte und Vorteile werden der Quelle zugeschrieben; keine unabhängige Messung.","en":"Reported values and benefits are attributed to the source; no independent measurement was made.","es":"Los valores y beneficios se atribuyen a la fuente; no hubo medición independiente.","fr":"Les valeurs et avantages sont attribués à la source; aucune mesure indépendante n’a été réalisée.","pt":"Valores e benefícios são atribuídos à fonte; não houve medição independente.","tr":"Bildirilen değerler ve yararlar kaynağa atfedilir; bağımsız ölçüm yapılmadı."},"sourceUrls":["https://aws.amazon.com/blogs/database/reducing-storage-initialization-impact-in-amazon-rds-for-postgresql-after-snapshot-restore/"],"title":{"ar":"دراسة AWS: التهيئة المسبقة لـPostgreSQL تقلل تأخر الاستعادة","de":"AWS-Studie: PostgreSQL-Vorwärmung verkürzt Wiederherstellungszeiten","en":"AWS study finds PostgreSQL prewarming cuts restore delays","es":"Estudio de AWS: el precalentamiento reduce demoras de restauración","fr":"Une étude AWS montre que le préchauffage réduit les délais de restauration","pt":"Estudo da AWS aponta que pré-aquecimento reduz atrasos na restauração","tr":"AWS çalışması: PostgreSQL ön ısıtması geri yükleme gecikmesini azalttı"},"type":"events","updatedAt":"2026-10-15T21:26:31Z"}],"version":1},"data_downloads":[{"formats":{"csv":"https://newsverum.com/api/v1/articles/aws-rds-postgresql-snapshot-restore-prewarming-test/data/source-report?lang=en&format=csv","json":"https://newsverum.com/api/v1/articles/aws-rds-postgresql-snapshot-restore-prewarming-test/data/source-report?lang=en&format=json"},"id":"source-report"}],"data_types":["events"],"editorial_illustration":{"alt":"Conceptual illustration of technology, processors and connected information.","asset_id":"newsverum-v1-technology","avif_variants":[{"height":320,"url":"https://newsverum.com/assets/newsverum/illustrations/v1/technology-480.avif","width":480},{"height":480,"url":"https://newsverum.com/assets/newsverum/illustrations/v1/technology-720.avif","width":720},{"height":640,"url":"https://newsverum.com/assets/newsverum/illustrations/v1/technology-960.avif","width":960},{"height":800,"url":"https://newsverum.com/assets/newsverum/illustrations/v1/technology-1200.avif","width":1200},{"height":1024,"url":"https://newsverum.com/assets/newsverum/illustrations/v1/technology-1536.avif","width":1536}],"credit":"Newsverum","documentary":false,"height":1024,"kind":"symbolic-editorial-illustration","language":"en","scope":"topic","url":"https://newsverum.com/assets/newsverum/illustrations/v1/technology-1536.webp","variants":[{"height":320,"url":"https://newsverum.com/assets/newsverum/illustrations/v1/technology-480.webp","width":480},{"height":640,"url":"https://newsverum.com/assets/newsverum/illustrations/v1/technology-960.webp","width":960},{"height":1024,"url":"https://newsverum.com/assets/newsverum/illustrations/v1/technology-1536.webp","width":1536}],"width":1536},"event_id":"event-fba5a086-e3be-590d-ba96-9e63445f13d2","event_period":"2026-10-14","event_period_basis":"event-or-reference-period","id":"aws-rds-postgresql-snapshot-restore-prewarming-test","image":null,"importance":0.6,"language":"en","modified_at":"2026-10-15T21:30:20+00:00","publication_basis":"publication-record","published_at":"2026-10-15T21:30:20+00:00","reading_minutes":1,"region":"world","relations":[],"section_illustration":{"alt":"Conceptual illustration of technology, processors and connected information.","asset_id":"newsverum-v1-technology","avif_variants":[{"height":320,"url":"https://newsverum.com/assets/newsverum/illustrations/v1/technology-480.avif","width":480},{"height":480,"url":"https://newsverum.com/assets/newsverum/illustrations/v1/technology-720.avif","width":720},{"height":640,"url":"https://newsverum.com/assets/newsverum/illustrations/v1/technology-960.avif","width":960},{"height":800,"url":"https://newsverum.com/assets/newsverum/illustrations/v1/technology-1200.avif","width":1200},{"height":1024,"url":"https://newsverum.com/assets/newsverum/illustrations/v1/technology-1536.avif","width":1536}],"credit":"Newsverum","documentary":false,"height":1024,"kind":"symbolic-editorial-illustration","language":"en","scope":"section","url":"https://newsverum.com/assets/newsverum/illustrations/v1/technology-1536.webp","variants":[{"height":320,"url":"https://newsverum.com/assets/newsverum/illustrations/v1/technology-480.webp","width":480},{"height":640,"url":"https://newsverum.com/assets/newsverum/illustrations/v1/technology-960.webp","width":960},{"height":1024,"url":"https://newsverum.com/assets/newsverum/illustrations/v1/technology-1536.webp","width":1536}],"width":1536},"slug":"aws-rds-postgresql-snapshot-restore-prewarming-test","sources":[{"checkedAt":"2026-10-15","name":"AWS Database Blog","publishedAt":"2026-10-14","url":"https://aws.amazon.com/blogs/database/reducing-storage-initialization-impact-in-amazon-rds-for-postgresql-after-snapshot-restore/"}],"summary":"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.","text":"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.\n\nAWS 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.\n\nThe 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.","title":"AWS study finds PostgreSQL prewarming cuts restore delays","topics":[],"translations":[{"api_url":"https://newsverum.com/api/v1/articles/aws-rds-postgresql-snapshot-restore-prewarming-test?lang=tr","language":"tr","url":"https://newsverum.com/tr/news/aws-rds-postgresql-snapshot-restore-prewarming-test"},{"api_url":"https://newsverum.com/api/v1/articles/aws-rds-postgresql-snapshot-restore-prewarming-test?lang=en","language":"en","url":"https://newsverum.com/en/news/aws-rds-postgresql-snapshot-restore-prewarming-test"},{"api_url":"https://newsverum.com/api/v1/articles/aws-rds-postgresql-snapshot-restore-prewarming-test?lang=ar","language":"ar","url":"https://newsverum.com/ar/news/aws-rds-postgresql-snapshot-restore-prewarming-test"},{"api_url":"https://newsverum.com/api/v1/articles/aws-rds-postgresql-snapshot-restore-prewarming-test?lang=fr","language":"fr","url":"https://newsverum.com/fr/news/aws-rds-postgresql-snapshot-restore-prewarming-test"},{"api_url":"https://newsverum.com/api/v1/articles/aws-rds-postgresql-snapshot-restore-prewarming-test?lang=es","language":"es","url":"https://newsverum.com/es/news/aws-rds-postgresql-snapshot-restore-prewarming-test"},{"api_url":"https://newsverum.com/api/v1/articles/aws-rds-postgresql-snapshot-restore-prewarming-test?lang=de","language":"de","url":"https://newsverum.com/de/news/aws-rds-postgresql-snapshot-restore-prewarming-test"},{"api_url":"https://newsverum.com/api/v1/articles/aws-rds-postgresql-snapshot-restore-prewarming-test?lang=pt","language":"pt","url":"https://newsverum.com/pt/news/aws-rds-postgresql-snapshot-restore-prewarming-test"}],"url":"https://newsverum.com/en/news/aws-rds-postgresql-snapshot-restore-prewarming-test"},"version":"1"}