Side-by-side benchmark comparison across agentic, coding, multimodal, knowledge, reasoning, and math workflows.
Mistral 8x7B
48
0/8 categoriesQwen3.5-27B
70
Winner · 7/8 categoriesMistral 8x7B· Qwen3.5-27B
Pick Qwen3.5-27B if you want the stronger benchmark profile. Mistral 8x7B only becomes the better choice if you would rather avoid the extra latency and token burn of a reasoning model.
Qwen3.5-27B is clearly ahead on the aggregate, 70 to 48. The gap is large enough that you do not need to squint at the spreadsheet to see the difference.
Qwen3.5-27B's sharpest advantage is in coding, where it averages 77.6 against 26.1. The single biggest benchmark swing on the page is LiveCodeBench, 23% to 80.7%.
Qwen3.5-27B is the reasoning model in the pair, while Mistral 8x7B is not. That usually helps on harder chain-of-thought-heavy tests, but it can also mean more latency and more token spend in real use. Qwen3.5-27B gives you the larger context window at 262K, compared with 32K for Mistral 8x7B.
BenchLM keeps the benchmark table and the operator tradeoffs on the same page so a better score does not hide a materially slower, pricier, or smaller-context model.
Runtime metrics show N/A when BenchLM does not have a sourced snapshot for that exact model. The scoring rules and freshness policy are documented on the methodology page.
| Benchmark | Mistral 8x7B | Qwen3.5-27B |
|---|---|---|
| AgenticQwen3.5-27B wins | ||
| Terminal-Bench 2.0 | 40% | 41.6% |
| BrowseComp | 47% | 61% |
| OSWorld-Verified | 38% | 56.2% |
| tau2-bench | — | 79% |
| CodingQwen3.5-27B wins | ||
| HumanEval | 32.3% | — |
| SWE-bench Verified | 28% | 72.4% |
| LiveCodeBench | 23% | 80.7% |
| SWE-bench Pro | 28% | — |
| Multimodal & GroundedQwen3.5-27B wins | ||
| MMMU-Pro | 42% | 75% |
| OfficeQA Pro | 56% | — |
| ReasoningQwen3.5-27B wins | ||
| MuSR | 61% | — |
| BBH | 67.1% | — |
| LongBench v2 | 57% | 60.6% |
| MRCRv2 | 53% | — |
| KnowledgeQwen3.5-27B wins | ||
| MMLU | 71.3% | — |
| GPQA | 64% | 85.5% |
| SuperGPQA | 62% | 65.6% |
| MMLU-Pro | 65% | 86.1% |
| HLE | 8% | — |
| FrontierScience | 56% | — |
| SimpleQA | 63% | — |
| Instruction FollowingQwen3.5-27B wins | ||
| IFEval | 78% | 95% |
| MultilingualQwen3.5-27B wins | ||
| MGSM | 74% | — |
| MMLU-ProX | 71% | 82.2% |
| Mathematics | ||
| AIME 2023 | 65% | — |
| AIME 2024 | 67% | — |
| AIME 2025 | 66% | — |
| HMMT Feb 2023 | 61% | — |
| HMMT Feb 2024 | 63% | — |
| HMMT Feb 2025 | 62% | — |
| BRUMO 2025 | 64% | — |
| MATH-500 | 73% | — |
Qwen3.5-27B is ahead overall, 70 to 48. The biggest single separator in this matchup is LiveCodeBench, where the scores are 23% and 80.7%.
Qwen3.5-27B has the edge for knowledge tasks in this comparison, averaging 80.6 versus 49.5. Inside this category, GPQA is the benchmark that creates the most daylight between them.
Qwen3.5-27B has the edge for coding in this comparison, averaging 77.6 versus 26.1. Inside this category, LiveCodeBench is the benchmark that creates the most daylight between them.
Qwen3.5-27B has the edge for reasoning in this comparison, averaging 60.6 versus 56.7. Inside this category, LongBench v2 is the benchmark that creates the most daylight between them.
Qwen3.5-27B has the edge for agentic tasks in this comparison, averaging 51.6 versus 41.1. Inside this category, OSWorld-Verified is the benchmark that creates the most daylight between them.
Qwen3.5-27B has the edge for multimodal and grounded tasks in this comparison, averaging 75 versus 48.3. Inside this category, MMMU-Pro is the benchmark that creates the most daylight between them.
Qwen3.5-27B has the edge for instruction following in this comparison, averaging 95 versus 78. Inside this category, IFEval is the benchmark that creates the most daylight between them.
Qwen3.5-27B has the edge for multilingual tasks in this comparison, averaging 82.2 versus 72.1. Inside this category, MMLU-ProX is the benchmark that creates the most daylight between them.
Get notified when new models drop, benchmark scores change, or the leaderboard shifts. One email per week.
Free. No spam. Unsubscribe anytime. We only store derived location metadata for consent routing.