Rongsong Shen a6a0bdf7cd docs(resource-accounting): explain why admission control doesn't query live ... Resource information for candidate hosts is injected into the scheduler once per session (worker push, cached in w->resvals/ w->resInUse); a single session then evaluates many jobs against many candidate hosts off that one cached snapshot without re-querying between decisions. Made the reason explicit: a live query per candidate-host check, at the volume a session performs, would be far too costly. This is a documentation clarification only -- no behavior change. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019QxaSzHRB7pmYFp4cVnwkA		2026-08-31 07:28:00 +00:00
..
settings	finalize configuration replication	2026-06-09 16:40:13 +08:00
specs	docs(scheduler-snapshot-job-allocation): sync spec.json phase to implementation-complete	2026-08-30 15:08:00 +00:00
steering	docs(resource-accounting): explain why admission control doesn't query live	2026-08-31 07:28:00 +00:00