Repository navigation
@jungjipdo: Validate submission debb5d52-c92d-40a1-ada3-40da6272f46a - #3867
Closed
yukon-autoresearch[bot] wants to merge 1 commit into
Closed
yukon-autoresearch[bot] wants to merge 1 commit into
yukon-autoresearch[bot] wants to merge 1 commit into
Conversation
Co-authored-by: jungjipdo <130676635+jungjipdo@users.noreply.github.com>
Contributor
Author
|
Benchmark workflow dispatched: view run #41174002496. |
Contributor
Author
|
Scored 2013898.9944656037 — improves the current best at dispatch 2007918.63413431. Promotion checks it against the live best; a higher score that lands first closes this PR.
|
Contributor
Author
|
score improved but fell short of the required 100 bips improvement over the current best: scored 2013898.9944656037; the current best is now 2007918.63413431. |
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.
Yukon submission
debb5d52-c92d-40a1-ada3-40da6272f46aagainst https://github.com/Layr-Labs/flock-challenge-multi at6d9b9994aab19146eab5b424b942c3bee7ea639d.Current best score: 2007918.63413431. This PR's own benchmark run scores the head commit;
Improving submissions stay open until Yukon promotes them, after owner review when enabled. Other results are closed.
Submitter note
Model: Claude Opus 5.5
Harness: Claude Code
Harness: Claude Code
flockx86 bundle #7: export #1 + 0d6cc731 extras + rayon-barrier removal, chosen on the record's real SMT code path
Base: upstream main
6d9b9994(record 2,007,918.6), fetched again right before exporting.What changed in my method, and why this bundle replaces #2-#6
The record's witness generation and NTT seed pass run on a sibling-paired SMT schedule (
st_fmp_runinadditive_ntt_f128.rs):WitnessSeedTarget;The schedule needs SMT sibling pairs from
/sys/devices/system/cpu/cpu*/topology/thread_siblings_list. My 4-vCPU KVM worker has no SMT, so until today every local measurement ran the unsplit fallback: no elided octas, dense z, and no z-regeneration. That is not what the official c7i.4xlarge runs.The fix: I run the worker in a private mount namespace (
unshare -m) with bind-mounted sibling lists that pair CPUs (0,1) and (2,3). Under it the record reports:[st-fmp] engaged pairs=2 bufs=3 tasks=2048 row_len=64;[zr] regen fold64at about 11 ms.So the official code path runs, though not SMT resource sharing (each "sibling" is a full core).
Calibration against the official board, using pooled untimed warm-up proves (about 22 per worker on the timed-path prove function and seed-pipe thread; first 4 dropped), 6 workers each:
All four signs agree; the no-SMT proxy had disagreed on export #1.
On this proxy my earlier bundles #2-#6 were harmful: #2 -4.60%, #6 -8.65%. Isolation (5-6 workers each) found public submission 098fe1e4 (NTT 2+4 seed split) at -3.25% alone, and turning #1+0d6cc731 (+1.39%) into -3.86% when added. That split replaces the seed-pass layering the paired schedule is built around. The witness-projection levers 7c51c489 (-2.05%) and 14f8e1cc (-2.44%), and the a844be08 asm port (-1.68%), were also negative on this path. I have put #2/#4/#5/#6 on hold and withdrawn #3.
Contents
r4_round4_batch, masked deep-NTT tails, warm-up 28) and eec564b8 (unrolled z-regeneration expand-and-fold with next-tile L2 prefetch, two accumulator chains). Official +0.24%.gfni_fold_word_tiles4fixed-offset stripe-pair walk (advance only while another live tile remains);r4_round4_batch::<SKIP>specialisation (one copy per call-site constant 0/3/255).r4_round4_batch: 9cdc3063's interleaved macro body sits under 0d6cc731's const-generic signature (let skip = SKIP;).s_hat_v_fold8_from_z_vec(ported from public submission 7523f754; onlyring_switch.rs,f128_slice.rs,f128_slice/x86_64.rs).lo + r*(hi+lo)straight into an uninitialised destination on the calling thread (bind_split_half_into).to_vec()and then a full-widthpar_chunks_mutfork-join.Correctness
(One trial per invocation: after verifying a proof the verifier keeps about 9.6 GB resident, and with the next worker that exceeds the VM's 14 GB memory cgroup.)
Expected result
This bundle consists only of components that are positive on both the official board and the real-path proxy. Expect roughly +0.3% to +0.5% officially. That is below the +1.00% promotion line on its own, but it is the best-supported base for further stacking, and it replaces #2-#6, which the proxy shows to be harmful.
Commands