Add benchmark link and NVMe footnote to Managed Postgres overview#6287
Conversation
|
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
4 Skipped Deployments
|
|
|
||
| - **Microsecond-level disk latency** instead of milliseconds | ||
| - **Unlimited local IOPS** without network bottlenecks | ||
| - **Unlimited local IOPS**<sup>[*](https://docs.aws.amazon.com/ec2/latest/instancetypes/gp.html#gp_instance-store)</sup> without network bottlenecks |
There was a problem hiding this comment.
- doesn't need to be link, can just be used as a reference section below
|
|
||
| For detailed benchmark results, see [Performance benchmarks](/docs/cloud/managed-postgres/benchmarks). | ||
|
|
||
| For see [AWS local NVMe limits for details](https://docs.aws.amazon.com/ec2/latest/instancetypes/gp.html#gp_instance-store). |
There was a problem hiding this comment.
This can refer to the start, like
- 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)
|
Docs PR opened: ClickHouse/mintlify-docs-dev#68 Added an NVMe footnote, a Performance benchmarks link, and an AWS local NVMe limits link to the Managed Postgres overview. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 320e339. Configure here.


Summary
Checklist
Note
Low Risk
Documentation-only edits with no runtime, security, or data-path impact.
Overview
The Managed Postgres overview doc now qualifies the “Unlimited local IOPS” bullet with a footnote marker and adds reader-facing pointers instead of leaving that claim standalone.
It links to the internal Performance benchmarks page for detailed numbers, and adds a short line with AWS EC2 instance store documentation (memory-, storage-, and CPU-optimized families) so “unlimited” is understood in terms of local NVMe limits on AWS.
Reviewed by Cursor Bugbot for commit d4f5954. Bugbot is set up for automated code reviews on this repo. Configure here.