feat: add remote-bench-e2e.yml for batch remote-bench dispatch#30
Merged
Conversation
Matrix-fans a JSON array of remote-bench configs to benchmark-tmpl.yml in one dispatch, mirroring e2e-tests.yml's fan-out pattern. Takes the config array directly instead of going through generate_sweep_configs.py, so it stays independent of the closed master-config schema.
This was referenced Jul 24, 2026
aistackdev
pushed a commit
that referenced
this pull request
Jul 24, 2026
…ndpoint) Adds remote-bench: benchmark an already-running, externally-managed inference endpoint instead of launching a server on the GPU runner. - benchmark_lib.sh: REMOTE_BASE_URL override in build_replay_cmd so aiperf points at an external endpoint instead of localhost. - benchmark-tmpl.yml: 6 optional remote-* workflow_call inputs/env vars, consumed only by *-remote-bench.sh recipes. - remote-bench-e2e.yml: single entrypoint, takes a JSON array of configs (one element for a smoke test, many for a full CCU-ladder sweep), matrix-fans to benchmark-tmpl.yml, then aggregates via collect-results + calc-success-rate. - Two model-agnostic *-remote-bench.sh recipes (dsv2lite fp8, glm5.2 fp4), the cluster:remote-bench runner label + non-GPU controller launcher (bench-client_01). - create-remote-bench skill: how to bring up a new recipe, including checking the endpoint's KV pool capacity to size a concurrency ladder, and the REMOTE_MAX_CONTEXT_LENGTH incident (a per-request cap is required, and even the model's nominal context window isn't automatically a safe value on small/dev GPUs). - sync-upstream + fork-changelog skills: since fork commits now live directly on main instead of a separate customization branch, syncing upstream is a real merge — fork-changelog lists every fork-only edit and why, sync-upstream is the procedure that checks against it. Background: issue #26/#28, PR #27/#30/#31/#34 (squashed into this single commit).
1 task
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
1 participant
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.
Summary
Adds
remote-bench-e2e.yml, a batch counterpart toremote-bench.yml: dispatch several remote-bench configs (different conc/duration/dataset variants) in one call, matrix-fanned tobenchmark-tmpl.ymlthe same waye2e-tests.ymlfans out master-config sweeps.Takes a JSON array of configs directly (
configsinput) rather than going throughgenerate_sweep_configs.py— keeps remote-bench independent of the closed master-config schema, same rationale asremote-bench.ymlitself (issue #26/#27).Test plan
benchmark-tmpl.ymlwiring work end to end