Evaluation
These are worker-under-orchestrator results, not solo-model accuracy. Concurrency is 64 top-level episodes. BrowseComp: 150 questions, 3 nodes, TP4 orchestrator and four independent TP1 workers. DR9K: 256 questions, 2 nodes, TP4 orchestrator and TP1/native DP4 workers. Full-answer repository manual grading protocol; not the canonical Gemini semantic judge. Empty/error episodes count wrong.
Table with columns: Orchestrator, BrowseComp, DR9K| Orchestrator | BrowseComp | DR9K |
|---|
| MiniMax-M2.7 | 97/150 (64.67%) | 111/256 (43.36%) |
| DeepSeek-V4-Flash | 97/150 (64.67%) | 148/256 (57.81%) |
| Nemotron Ultra | 104/150 (69.33%) | 139/256 (54.30%) |
| MiMo-V2.5 | 106/150 (70.67%) | 143/256 (55.86%) |
| Nemotron Super | 86/150 (57.33%) | 131/256 (51.17%) |
| Inkling-Small | 104/150 (69.33%) | 147/256 (57.42%) |
Complete report includes latency settings, difficulty scores, observed role tokens/cache and separate theoretical worker prefix reuse.
BrowseComp traces · DR9K traces.
Use the report's evaluator, benchmark-specific chat templates, search tools and budgets to reproduce the worker results; generic chat generation alone does not reproduce this setup.