Merge pull request #6296 from ClickHouse/yashpreet/remove-benchmarks-overview

dhtclk · web-flow · commit 6788d9545a44 · 2026-05-27T18:56:16.000-05:00
Remove Managed Postgres benchmarks page and link to blog post
diff --git a/docs/cloud/managed-postgres/benchmarks.md b/docs/cloud/managed-postgres/benchmarks.md
diff --git a/docs/cloud/managed-postgres/overview.md b/docs/cloud/managed-postgres/overview.md
@@ -32,7 +32,9 @@ Managed Postgres uses NVMe storage that is physically attached to the same serve
 
 For Postgres workloads that are primarily throttled by disk IOPS and latency, this translates to faster ingestion, quicker vacuums, lower tail latency, and more predictable performance under load.
 
-For detailed benchmark results, see [Performance benchmarks](/cloud/managed-postgres/benchmarks). 
+:::note
+Learn how fast Postgres is on NVMe disks from [performance benchmarks](https://clickhouse.com/blog/postgresbench).
+:::
 
 For local NVMe limits on AWS see [Memory optimized](https://docs.aws.amazon.com/ec2/latest/instancetypes/mo.html#mo_instance-store), [Storage optimized](https://docs.aws.amazon.com/ec2/latest/instancetypes/so.html#so_instance-store), [CPU optimized](https://docs.aws.amazon.com/ec2/latest/instancetypes/gp.html#gp_instance-store).
 
diff --git a/sidebars.js b/sidebars.js
@@ -401,7 +401,6 @@ const sidebars = {
             'cloud/managed-postgres/monitoring/metrics',
           ],
         },
-        'cloud/managed-postgres/benchmarks',
         'cloud/managed-postgres/openapi',
         'cloud/managed-postgres/faq',
       ],
