Rongsong Shen
a6a0bdf7cd
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 |
||
|---|---|---|
| .. | ||
| api-standards.md | ||
| build-deployment.md | ||
| config-design.md | ||
| error-handling.md | ||
| ha-async-io.md | ||
| persistence.md | ||
| product.md | ||
| resource-accounting.md | ||
| roadmap.md | ||
| scheduler-driver-equivalence.md | ||
| security.md | ||
| structure.md | ||
| tech.md | ||
| testing.md | ||