Scaling by the clock: schedule windows with their own min and max, prewarm, control.timezone
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
74429f1c00
commit
bce54f0941
14 files changed
+382
-9
No files matched your search
+6
-1
@@ -482,7 +482,12 @@ portal is not done — the page shows; the console and ctl change.
|
||||
**SLO-based admission and token-level metrics (S–M).** TPOT and
|
||||
inter-token histograms, output tokens/s per model and tenant in
|
||||
`router/metrics.go`; use `catalog.SLO` in `admission/saturation.go`.
|
||||
14. **Scheduled and warm-pool autoscaling (S–M).** Time-of-day min/max,
|
||||
14. **Done (branch `features-c2`):** `scaling.schedule` (days, from, to,
|
||||
min, max; past midnight), `scaling.prewarm`, `control.timezone`;
|
||||
queue-depth scaling was there already. Left: `ctl scale` sets min and
|
||||
max only (a schedule is set in the definition); scaling for an SLO
|
||||
rather than for queue depth.
|
||||
**Scheduled and warm-pool autoscaling (S–M).** Time-of-day min/max,
|
||||
pre-warm, queue-depth scaling in `catalog.Scaling`,
|
||||
`control/reconciler/demand.go`, `headroom.go`.
|
||||
15. **Secrets management (S–M).** Vault/KMS for `api_key_file`, the DSN, the
|
||||
|
||||
Reference in new issue
Block a user