This canonical paper page includes Commercialization Proof and Related Resources.
ARXIV:2605.20982 · LLM INFRASTRUCTURE · SUBMITTED 21 MAY · 20:33 UTC · FRESHNESS STALE
ARXIV:2605.20982LLM INFRASTRUCTURESUBMITTED 21 MAY · 20:33 UTCFRESHNESS STALEBole Ma · Jan Eitzinger · Harald Koestler · Gerhard Wellein · arXiv
DODOCO, a cross-architecture observatory, reveals that current MoE dispatch mitigations and benchmarks are flawed, identifying two stable architecture bands for interconnect design.
Opportunity summary
Pain DODOCO, a cross-architecture observatory, reveals that current MoE dispatch mitigations and benchmarks are flawed, identifying two stable architecture bands for interconnect design.
Evidence 0 refs | 3 sources | 50% coverage
Blocker Evidence unverified
DODOCO, a cross-architecture observatory, reveals that current MoE dispatch mitigations and benchmarks are flawed, identifying two stable architecture bands for interconnect design. All four rest on two assumptions about the workload.
AlltoAll dispatch is the dominant bottleneck of MoE expert parallelism, and the interconnect community has responded with four families of mitigations: predictive sample placement, adaptive expert relayout, hierarchical collectives, and EP-aware topology. All four…
ScienceToStartup currently rates this 4.0/10 on the public viability pass. These bands, not the EP degree or the mock-data profile, are the right workload input to AlltoAll-aware interconnect and dispatch design. Code availability is…
LLM Infrastructure moved forward this cycle; last verified May 2026. Public score 4.0/10. Production flags indicate code availability.
Continue into Read for claims, analysis, references, and neighboring papers.
mobile layout uses overflow-hidden min-w-0 break-wordsOpportunity summary
Score4.0Public score shown from the verified overall while the stale axis breakdown refreshesAnalysis summary
DODOCO, a cross-architecture observatory, reveals that current MoE dispatch mitigations and benchmarks are flawed, identifying two stable architecture bands for interconnect design.
Loading BUILD…
Paper Pack
10.48550/arXiv.2605.20982DODOCO, a cross-architecture observatory, reveals that current MoE dispatch mitigations and benchmarks are flawed, identifying two stable architecture bands for interconnect design.
Abstract
AlltoAll dispatch is the dominant bottleneck of MoE expert parallelism, and the interconnect community has responded with four families of mitigations: predictive sample placement, adaptive expert relayout, hierarchical collectives, and EP-aware topology. All four rest on two assumptions about the workload. The first is that routing imbalance is correctable by the system layer. The second is that the mock-token benchmarks evaluating them faithfully represent production routing. We introduce DODOCO to test both assumptions. We instrument five MoE checkpoints spanning five sequence-mixer designs (DeepSeek-V2-Lite MLA, DeepSeek-MoE-16B MHA, Qwen3-30B GQA, Nemotron-30B Mamba-2, Qwen3.5-35B GDN) under a 5 by 6 grid of data conditions plus a matched EP scan from 4 to 32 ranks on H100s; both assumptions fail. Scaling EP changes the per-expert max/mean token ratio by at most 5% within every architecture's measurable range: the straggler is intrinsic to the routing decision the model makes, not to how its experts land on ranks. Mock tokens overestimate routing Gini by up to a factor of 2.35 and fabricate a batch-size scaling trend that vanishes the moment real text replaces random IDs. A third pattern, unexpected, emerges from the same matrix: the five architectures cleave into two stable bands. MHA and Mamba-2 (data-resilient) drop to Gini 0.105 and 0.150 on wikitext. MLA and GDN (persistently concentrated) stay above 0.24 on every real-text condition and reach 0.29 to 0.38 on mock. GQA is the intermediate case. These bands, not the EP degree or the mock-data profile, are the right workload input to AlltoAll-aware interconnect and dispatch design.
Source availability
PDF linkedThe paper record includes a public PDF URL.
Extraction status
Parse run linkedA document parse run is attached to this paper.
Proof status
unverified0 refs; 3 sources; 50% coverage.
What was readable
Derived fallback: Estimated from adjacent evidence; not verified from source.
Viability
Time to MVP
Commercial
Export
Preparing verified analysis
Dimensions overall score 4.0
PROBLEM
DODOCO, a cross-architecture observatory, reveals that current MoE dispatch mitigations and benchmarks are flawed, identifying two stable architecture bands for interconnect design. All four rest on two assumptions about the workload.
METHOD
AlltoAll dispatch is the dominant bottleneck of MoE expert parallelism, and the interconnect community has responded with four families of mitigations: predictive sample placement, adaptive expert relayout, hierarchical collectives, and EP-aware topology. All four rest on two as...
RESULT
ScienceToStartup currently rates this 4.0/10 on the public viability pass. These bands, not the EP degree or the mock-data profile, are the right workload input to AlltoAll-aware interconnect and dispatch design. Code availability is flagged in the production record; the public...
WHY NOW
LLM Infrastructure moved forward this cycle; last verified May 2026. Public score 4.0/10. Production flags indicate code availability.
Abstract-backed public claims while anchored extraction refreshes.
DODOCO, a cross-architecture observatory, reveals that current MoE dispatch mitigations and benchmarks are flawed, identifying two stable architecture bands for interconnect design. All four rest on two assumptions about the workload.
Abstract-backed fallback claim; anchored extraction has not materialized a public claim row yet.
partial
AlltoAll dispatch is the dominant bottleneck of MoE expert parallelism, and the interconnect community has responded with four families of mitigations: predictive sample placement, adaptive expert relayout, hierarchical collectives, and EP-aware topology. All four rest on two assumptions about the workload.
Abstract-backed fallback claim; anchored extraction has not materialized a public claim row yet.
partial
ScienceToStartup currently rates this 4.0/10 on the public viability pass. These bands, not the EP degree or the mock-data profile, are the right workload input to AlltoAll-aware interconnect and dispatch design. Code availability is flagged in the production record; the public repository link still needs proof alignment.
Abstract-backed fallback claim; anchored extraction has not materialized a public claim row yet.
partial
LLM Infrastructure moved forward this cycle; last verified May 2026. Public score 4.0/10. Production flags indicate code availability.
Abstract-backed fallback claim; anchored extraction has not materialized a public claim row yet.
partial
Paper-native neighborhood for concepts, methods, materials, markets, and competitors. Missing lanes stay labeled instead of disappearing behind commercialization gates.
Concepts
Methods
Materials
Markets
Competitors
DODOCO, a cross-architecture observatory, reveals that current MoE dispatch mitigations and benchmarks are flawed, identifying two stable architecture bands for interconnect design.
Segment
LLM Infrastructure
Adoption evidence
No public code link in the paper record yet
Commercial read
4.0/10 public viability
Direct
Adjacent
Substitute
Unknown
No indexed public discussion is attached to 2605.20982 yet. That is a visibility signal, not a blank module: the monitor is watching the public channels below.
Hacker News
Not indexed yet
Not indexed yet
Bluesky
Not indexed yet
Preview the source document here, or use the hero PDF action for a new tab.
Reference metadata is not materialized in the public index yet. The source PDF remains the authority; cache refresh is optional.
CITED BY
No citing papers are indexed in the public S2S graph yet. This is an explicit zero-signal state, not a hidden lookup.
Foundation
Commercially relevant
Conflicting
Owned Distribution
Get the weekly shortlist of commercializable papers, benchmark movers, and proof receipts that matter for product execution.
2/3 checks · 67%
Build Passport
Build passport pending - Proof Lab budget No verified cost estimate / $7.00 cap
status
missing
reason
passport_row_missing
proof status
unverified
cost/budget
No verified cost estimate
confidence low
next verification path
Build brief missing until Build Passport data exists.
Source missing: Build Passport payload.
Experiment plan missing until prototype path is available.
No prototype path attached.
Validation checklist missing until required assets, cost, and regulatory flags are verified.
No checklist artifact is attached to the Build Passport payload.
Derived signals show verified:false until source-backed receipts exist.
Evidence coverage
OpportunityKernel evidence_receipt
0 refs / 3 sources / 50% coverage
stale
Verify missing sources before using this as buyer proof. verified:false
Build readiness
BuildPassport EvidenceState
passport absent
stale
Run Proof Lab or inspect typed missing state. verified:false
Artifact maturity
GitHub and Hugging Face maturity payloads
No public artifact surface observed
stale
Open source artifacts or mark the gap as missing. verified:false
Technical feasibility
partial
Current read
Runnable path is not fully verified.
Evidence
No Build Passport payload attached.
Gaps
Next test
Run minimal reproduction from the Build Passport prototype path.
Market urgency
missing
Current read
Buyer urgency is not verified from source.
Evidence
0 references, 3 sources, 50% evidence coverage.
Gaps
Next test
Collect buyer interview, deployment evidence, or cited demand signal.
Buyer clarity
missing
Current read
No budget owner is verified for this paper.
Evidence
Build tab has no CRM, procurement, or operator source.
Gaps
Next test
Map target operator, economic buyer, and procurement trigger.
Defensibility
missing
Current read
Defensibility signals are missing.
Evidence
No defensibility receipt attached.
Gaps
Next test
Refresh defensibility bars with source receipts.
Integration burden
missing
Current read
No public implementation surface observed.
Evidence
No GitHub or Hugging Face payload attached.
Gaps
Next test
Write integration checklist from prototype path and target workflow.
Capital intensity
missing
Current read
No observed cost estimate is verified.
Evidence
Cost passport has no observed_usd value.
Gaps
Next test
Run cost passport or mark the cost field not applicable.
Regulatory load
missing
Current read
No regulatory classification is attached.
Evidence
Build Passport ledger does not include regulatory flags.
Gaps
Next test
Classify regulatory flags before commercialization planning.
No named scientific founder assigned.
Paper authors are not treated as operators without consent.
People
No named person assigned.
Gaps
Next verification path
Prototype owner missing.
Build Passport does not name an implementer.
People
No named person assigned.
Gaps
Next verification path
Operator workflow not sourced.
No buyer or workflow interview attached.
People
No named person assigned.
Gaps
Next verification path
No GTM owner verified.
No CRM or outreach source attached.
People
No named person assigned.
Gaps
Next verification path
Regulatory need unclassified.
No clinical or regulatory source attached.
People
No named person assigned.
Gaps
Next verification path
ARTIFACTS
No public artifacts yet.
DEFENSIBILITY
Defensibility and confidence evidence pending.
WATCHTOWER
No verified watchtower monitor rows yet.
FORESIGHT
No prediction yet — minted on next Foresight batch.
OPPORTUNITYKERNEL CHANGES SINCE LAST VIEW
No verified OpportunityKernel changes since the last view.
COMPETITIVE LANDSCAPE UPDATES
No verified competitive landscape changes yet.
RELATED PAPER UPDATES
No verified related paper changes yet.
SIGNAL CANVAS HISTORY AND DELTAS
No Signal Canvas history deltas yet.
TIMELINE
Save this paper to start tracking momentum - commits, demos, and score changes appear here.
No tracked events yet.
Score trend will appear after multiple data points.
BUZZ
Buzz trend pending.