Repository navigation
Conversation
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.
Problem and result
This results-only report adds Linux/RTX 3090 evidence for the existing mixed-size resident exchange rotation switch. One unmodified engine 0.1.55 build at
c62d5e3a15b40ea51c96aae9e8d36928965f53abran four fresh-process A→B→B→A starts; onlySTRATA_EXCHANGE_ROTATEchanged.Code ranges slightly overlap; Chinese ranges are separate. All four natural-stop repairs passed 14/14 checks, with lengths A 499/311 and B 352/1070 tokens. Repair E2E is reported per output, including its higher on-arm median, rather than presented as equal-work latency improvement. Outputs also vary within each arm.
Related discussion
Existing implementation and maintainer measurements: #2042. This PR adds measurements and explanation; it does not resubmit the implementation or change defaults.
Approach
Report, raw records and reproduction include all 28 requests, sanitized logs/configuration, the frozen expert profile, engine/client timings, output text, grader and artifact hashes. An optional standalone HTML explains ownership transfer and displays the same data.
The official 16 staging slots were retained, and CPU fallback occurred. GPU cache geometry matched across all starts. The GPU retains the previous hardware experiment state, disclosed in the report; both arms use that state.
The memory formula covers distinct block sizes and async bounce buffers:
Here the exchange pool grows from 138.281 to 365.625 MiB: +227.344 MiB pinned host RAM, with GPU expert-cache capacity unchanged. Ownership metadata and driver mapping costs are outside this payload equation and were not separately measured.
Validation
Passed:
build.json,build-0.log,build-1.login the report directory.ctest --test-dir <build> -R '^(exchange_storage_test|file_expert_source_test)$' --output-on-failureand<build>/file_expert_source_test --rotation-gpu: exit 0, logs attached.python3 verify_public.py .from the report directory: hashes, 28 raw records, timing formulas, summary statistics, score counts and toggle-only fingerprint environment verified.Failed: A first observer admission attempt found no engine PID because it only searched the server main thread's child list. It ended before any inference request. Error/logs and recovery are retained separately; the corrected observer searched all threads and a fresh directory holds the complete ABBA. No inference request was retried or replaced.
Not run: standard benchmark protocol, Compute Sanitizer, native token-ID/logit parity, other hardware/backends and browser screenshot verification for the optional HTML.
Limits
This is a custom workload report under COMMUNITY_BENCHMARKS.md, not a standard-protocol or approved result. It covers one VM, GPU, quantization and one fixed repair task. Publisher revisions are unknown; actual local model/pack/tokenizer SHA-256 values are attached. Seven workers and approximately 295 MiB initial free VRAM trigger tuning warnings, preserved with both arms fixed. Actual GPU paging and the cause of output differences were not isolated. No engine code, preset, default or top-level benchmark index is changed.
AI-assisted experiment orchestration and report preparation with Codex.