Skip to main content

Benchmark survey

The short survey behind the presets: which benchmark measures which ability, why those were chosen for small fine-tuned models, which harness runs them, and the pitfalls the design guards against. Sources are at the end.

Assumptions. Models are the catalog's (Qwen3-0.6B/1.7B, Qwen3.5-0.8B/2B, Qwen3-Embedding-0.6B) and their fine-tunes; one GPU or a Mac; the comparison that matters is checkpoint against checkpoint and against the base model, not against frontier models. Survey depth: light (direct searches, no literature review).

Benchmarks by what they tell​

AxisBenchmarkWhy this oneHarness task
KnowledgeMMLU-Redux, MMLU-Prowhat the Qwen3.5 small-model cards report, so base-model numbers exist to compare withmmlu_redux, mmlu_pro
Hard knowledgeGPQA Diamondgraduate-level, Google-proof; low for small models but moves with reasoning traininggpqa
MathGSM8K, MATH-500saturated for frontier models, still discriminative for small and fine-tuned onesgsm8k, minerva_math/math500
Instruction followingIFEvalverifiable constraints, no judge; reported for Qwen3.5-0.8B/2B (52.1 / 61.2 non-thinking)ifeval
Commonsense, regression panelHellaSwag, ARC-Challenge, TruthfulQA, Winograndecheap log-likelihood tasks; a fine-tune that forgets shows up here firsthellaswag, arc_challenge, truthfulqa_mc2, winogrande
CodeHumanEval+, MBPP+ (EvalPlus)execution-based; only when the fine-tune targets codehumaneval, mbpp (EvalPlus variants)
KoreanKMMLU, KMMLU-Redux/Pro, HAE-RAE Bench, KoBEST, CLIcK, HRM8Koriginal Korean exams and culture, not translations; all present in lm-evaluation-harnesskmmlu, haerae, kobest, click, hrm8k
Long contextRULER, LongBenchonly when the fine-tune changes context handling; expensiveruler, longbench
Decision modelsJevBench (easy, standard, hard tiers; 231 public items), plus the Jeeves transfer panel: MMLU, MMLU-Pro, PAWS, QNLI, SciQ, TweetEval offensive, Emotionthe reference evaluation of the decision recipes' origins; accuracy and ECE, with and without reasoning, plus latencyown runner (DecisionMethod.evaluate + JevBench format)
EmbeddingsMTEB v2: MTEB(eng, v2) retrieval subset; Korean retrieval tasks from MMTEBthe standard; Qwen3-Embedding is reported on itmteb package

Base-model reference points (Qwen3.5 small-model cards, non-thinking unless noted):

BenchmarkQwen3.5-0.8BQwen3.5-2B
MMLU-Pro29.7 (thinking 42.3)55.3 (thinking 66.5)
MMLU-Redux48.5 (thinking 59.5)69.2 (thinking 79.6)
IFEval52.161.2
SuperGPQA16.930.4
MMMLU34.156.9

These numbers are the vendor's, under the vendor's prompts and decoding. The plan treats them as orientation only: the channel measures the base model itself, under the same settings as the checkpoints, and that is the baseline.

Harness​

  • lm-evaluation-harness (EleutherAI) for every static benchmark above: 200+ YAML-defined tasks, the Korean tasks included, local Hugging Face checkpoints via --model hf, log-likelihood and generative tasks, per-task standard errors. It is the default choice of the field for this kind of static scoring.
  • mteb for embedding models.
  • An own runner for decision models: the recipes' DecisionMethod.evaluate already computes calibrated accuracy, NLL and ECE with and without reasoning; it needs a JevBench reader and a latency measurement.
  • Not needed now: Inspect AI (agentic and tool-use evaluation), HELM (multi-metric profiling of many models), LLM-as-judge suites (a judge adds cost and bias that a checkpoint comparison does not need).

Pitfalls the design must handle​

Source: evaluation/README.md. This page is generated; edit the source and run npm run sync.