coulomb/resource-control
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Review capped Vergabe comparison without changing allocation

Browse source 
Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a15374-f59f-7a31-86d2-d23b5d2ed181
This commit is contained in:
tegwick 2026-10-19 15:20:33 +02:00
parent c6dcad5a58
commit e3e996fc95
2 changed files with 21 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
workplans/RESOURCE-WP-0008-custodian-allocation-review.md
View file

@ -47,8 +47,10 @@ priority: high
state_hub_task_id: "1f538441-8b45-5d37-aeb3-345204b75117"
```
Consume the in-progress isolated app-container comparison at the existing
1000m CPU and 1Gi memory limits. The 60m request is a contention share/reservation,
Initial comparison received at Vergabe `bfd1a2d`: zero errors and ordinary p95
412ms under the existing 1000m CPU and 1Gi memory limits. The retained review
supports keeping those limits provisionally; edits, startup/restart, bursts and
target-runtime contention still need coverage. Consume those remaining results. The 60m request is a contention share/reservation,
not a CPU cap. Compare complete latency/error and CPU/throttle/memory evidence,
retain synthetic pacing assumptions and configurable safety factors, and state
what the sample cannot establish about production contention and shared services.