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 | 100/150 (66.67%) | 120/256 (46.88%) |
| DeepSeek-V4-Flash | 99/150 (66.00%) | 148/256 (57.81%) |
| Nemotron Ultra | 98/150 (65.33%) | 143/256 (55.86%) |
| MiMo-V2.5 | 113/150 (75.33%) | 153/256 (59.77%) |
| Nemotron Super | 92/150 (61.33%) | 128/256 (50.00%) |
| Inkling-Small | 110/150 (73.33%) | 158/256 (61.72%) |
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.