feat(compute): Add perf test for compute startup time breakdown #11198
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
We had a recent Postgres startup latency (
start_postgres_ms
) degradation, but it was only caught with SLO alerts. There was actually an existing test for the same purpose --start_postgres_ms
, but it's doing only two starts, so it's a bit noisy.Summary of changes
Add new compute startup latency test that does 100 iterations and reports p50, p90 and p99 latencies.
Part of https://github.com/neondatabase/cloud/issues/24882