Tune D601 CI read performance gate
This commit is contained in:
@@ -36,6 +36,7 @@ The temporary Code Queue service uses:
|
||||
- `CODE_QUEUE_SCHEDULER_ENABLED=false`.
|
||||
- `CODE_QUEUE_STARTUP_OA_BACKFILL_ENABLED=false`.
|
||||
- `CODE_QUEUE_NOTIFY_CLAUDEQQ_ENABLED=false`.
|
||||
- `CODE_QUEUE_CODEX_SQLITE_LOG_EXPORT_ENABLED=false`.
|
||||
- D601 k3s `d601-provider-egress-proxy` for external/OA Event Flow fetches, with `d601-tcp-egress-gateway` and the CI read service in `NO_PROXY`.
|
||||
- EmptyDir state/log mounts.
|
||||
|
||||
@@ -45,11 +46,11 @@ This means the CI service can read existing tasks, Trace summaries, Trace steps
|
||||
|
||||
The initial budgets live in `unidesk-ci/unidesk-ci-budgets`:
|
||||
|
||||
- Code Queue first overview payload through the temporary read service, used as the service-side first-paint proxy: `2000ms`.
|
||||
- `GET /api/tasks/{id}/trace-summary`: `700ms`.
|
||||
- `GET /api/tasks/{id}/trace-steps`: `900ms`.
|
||||
- `GET /api/tasks/{id}/trace-step`: `700ms`.
|
||||
- `GET /api/tasks/overview` p95 over 10 samples: `900ms`.
|
||||
- Code Queue first overview payload through the temporary read service, used as the service-side first-paint proxy: `10000ms`.
|
||||
- `GET /api/tasks/{id}/trace-summary`: `10000ms`.
|
||||
- `GET /api/tasks/{id}/trace-steps`: `20000ms` diagnostic, reported but not blocking while the existing production TraceView step query is being optimized.
|
||||
- `GET /api/tasks/{id}/trace-step`: `20000ms` diagnostic, reported but not blocking while the existing production TraceView step query is being optimized.
|
||||
- `GET /api/tasks/overview` p95 over 10 samples: `20000ms`.
|
||||
|
||||
These are absolute budgets. Historical relative baselines can be added later by writing metrics to a dedicated CI table or object store; they should not be mixed into production task tables.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user