Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/cloud/managed-postgres/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,11 +27,15 @@
Managed Postgres uses NVMe storage that is physically attached to the same server as your database. This architectural difference delivers:

- **Microsecond-level disk latency** instead of milliseconds
- **Unlimited local IOPS** without network bottlenecks
- **Unlimited local IOPS**<sup>\*</sup> without network bottlenecks
- **Up to 10x faster performance** for disk-bound workloads at the same cost

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).

Check warning on line 35 in docs/cloud/managed-postgres/overview.md

View workflow job for this annotation

GitHub Actions / vale

ClickHouse.EOLWhitespace

Remove whitespace characters from the end of the line.

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).

## Native ClickHouse integration {#clickhouse-integration}

Managed Postgres integrates natively with ClickHouse to bring transactions and analytics together without complex ETL pipelines.
Expand Down
Loading