baseline arm PR105.0: single-machine dual-GPU (no RPC), PR #110 config reference - #111
Open
ddvnguyen wants to merge 2 commits into
Open
baseline arm PR105.0: single-machine dual-GPU (no RPC), PR #110 config reference#111ddvnguyen wants to merge 2 commits into
ddvnguyen wants to merge 2 commits into
Conversation
Owner
Author
|
Amended the launch spec (leader review finding): added the flags the 747.0 reference yml sets that were missing from the literal command — |
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.
Baseline arm derived from the PR #110 verified config with the topology reduced to a single machine: both GPUs in one
llama-serverprocess, RPC peer removed. Binary and all other knobs identical to PR #110 — only the launch topology changes.Commits
docs/arms/pr105-single-machine-baseline.md): config-deltas table vs PR feat(server): --parallel-ctx-threshold admission gate + UM prefetch net (hydra#747 baseline) #110, canonical launch line, hypothesis, verification plan with pass criteria, test plan.Config deltas vs PR #110 rig
rpc-serveron CUDA1 (3060)-dev CUDA0,CUDA1-sm row -ts 27,38, threshold 100000,-np 2, K q8_0 / V q5_1,--spec-type draft-mtp, UM on, FA-all-quants buildGGML_RPC=ONstays in the build so one binary serves this arm and the upcoming PR103.0 (GDN cache-cpy fusion) / PR104.x (mixed-quant row sharding) arms.Hypothesis
Prior single-machine trial showed dropping RPC does not materially change decode — the wall is the 3060's bandwidth x VRAM-forced share, not RPC overhead. Expected: within-noise parity with the PR #110 bar. Value of the arm:
Verification plan (arm102 bars as reference)
Primary cell only for first pass; secondary cell (kv_unified on / V q4_1, bar 38.4) once primary passes.
Test plan
GGML_CUDA_FORCE_CUBLASoff/health200, both devices in device logAI usage disclosure: YES — arm spec and PR body drafted by AI (opencode) from the PR #110 verified config and local flag verification (
common/arg.cpp,docs/speculative.md);-c 296000(per-slot 148000 x 2) is carried from the arm102 record and flagged in the doc for confirmation against the arm102 yml before first boot. Repo owner to verify launch line on the rig before running.