Repository navigation
feat: the cluster configs, and the plan that says whether a run can work - #53
Merged
Merged
Conversation
These were written, tested, and then stranded on an unmerged branch while the
package was restructured. They are the deployment half of the real-fleet run and
main still had only the old vendored cluster.yaml.
python -m infra.render infra/config/single.yaml --plan
gpu-1 A100 x1 using 1/1
vllm-engine-0 TP=1 PP=1 1 GPU :8000 Qwen/Qwen2.5-7B-Instruct
22GB KV = ~384k tokens (~12 seqs at max_model_len 32768)
max_num_seqs=64 -> KV binds only above ~6.0k tokens/request;
below that the SCHEDULER binds
so a KV policy can fire only if the experiment sends
requests longer than ~6.0k tokens
That last line is the whole value: it is readable before renting anything, and it
is the difference between an hour that produces a finding and an hour that produces
a flat signal for a reason nobody noticed.
python -m infra.render infra/config/single.yaml --serve
Emits the `vllm serve` line from the same config the manifests come from, so the
bare-VM path cannot drift from it. infra/setup/lambda_vllm.sh is the reason this
matters: it hardcodes gpu-memory-utilization 0.85 against the config's 0.90 and
omits --max-num-seqs altogether — which is precisely the flag that decides whether
KV binds before the scheduler, and therefore whether a KV-pressure policy can fire
at all. A test asserts both flags appear.
single.yaml now declares ONE host rather than inheriting four. base.yaml carries
four from when the fleet had four instances, and a plan listing three machines with
"(no pools placed here)" buries the one line that matters under hosts nobody rented.
That changed a test's premise rather than breaking it: the variants no longer share
`hosts`, because a single-GPU config and a four-GPU disaggregated one genuinely need
different fleets. The invariant is now model, engine, overflow, admission and
placement — the things a comparison actually depends on.
Also drops infra/config/cluster.yaml and infra/providers/ (the Modal path), both
superseded.
220 passed, lint clean. infra/ is not part of the package; the wheel is unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
These were written and tested, then stranded on an unmerged branch while the package was restructured.
mainstill had only the old vendoredcluster.yaml, and this is the deployment half of the real-fleet run.The plan is the point
That last line is readable before renting anything, and it's the difference between an hour that produces a finding and an hour that produces a flat signal for a reason nobody noticed.
--serve, so the bring-up can't drift from the configinfra/setup/lambda_vllm.shis why this matters: it hardcodesgpu-memory-utilization 0.85against the config's0.90and omits--max-num-seqsentirely — which is exactly the flag that decides whether KV binds before the scheduler, and therefore whether a KV-pressure policy can fire at all. A test asserts both flags appear in the generated command.One host, not four
single.yamlnow declares one host rather than inheritingbase.yaml's four. Those four are from when the fleet had four instances, and a plan listing three machines with(no pools placed here)buries the line that matters under hardware nobody rented.That changed a test's premise rather than breaking it. The variants no longer share
hosts, because a single-GPU config and a four-GPU disaggregated one genuinely need different fleets. The invariant is nowmodel,engine,overflow,admission,placement— the things a comparison actually depends on. Forcinghoststo agree was the thing producing the phantom machines.Also drops
infra/config/cluster.yamlandinfra/providers/(the Modal path), both superseded.220 passed, lint clean.
infra/is not part of the package, so the wheel is unchanged.