b70-optimization-lab

Rapid Model Snapshots On B70

This lane is for quick, honest short-context decode snapshots across practical models on the 4x Intel Arc Pro B70 system. The goal is not to deeply optimize every model immediately. The goal is to get a reproducible, reasonably tuned baseline for useful model families, publish only strict-valid final rows, and leave enough notes that a future deeper lane can resume without rediscovery.

Current Policy

Final Gate

Headline results require:

Diagnostic runs can be looser, but must be labeled diagnostic and never promoted or submitted.

Candidate Priority

  1. Qwen3 30B-A3B / Qwen3-Coder 30B-A3B: best new vLLM/XPU target because the Intel/vLLM path is likely to support this MoE family directly. Start with GPTQ/INT4 or dynamic-FP8 style paths if available, then use GGUF as fallback.
  2. Mistral Small 3.2 24B Instruct GGUF: first llama.cpp dense-model target, useful quality/performance reference, likely to fit one B70 at Q4/Q6/Q8.
  3. Gemma 4 12B INT4/AutoRound or GGUF: small high-throughput production baseline and useful vLLM vs llama.cpp comparison.
  4. Phi-4 family: smaller high-throughput reference; include if setup is quick.
  5. DeepSeek-Coder / DeepSeek-R1-Distill references: include when the selected Q4+ file fits one B70 cleanly and gives users a useful expected-performance row without a deep optimization pass.

Do not spend rapid-lane time on Kimi K2.x, GLM 5.2, DeepSeek V4 Flash, or other models whose local footprint clearly exceeds a clean one-B70 or practical TP setup. Record them as skipped with the reason instead.

Per-Model Workflow

  1. Record model source, exact file/revision, quantization, size, and storage location.
  2. Start from a conservative baseline: one GPU, no cache reuse, short context, deterministic sampling, no speculation unless the model/runtime has a proven verifier path.
  3. Run a fast diagnostic decode screen to verify the endpoint and rough speed.
  4. Try quick knobs that historically mattered: ctx, batch, ubatch, FlashAttention, VMM, graph/JIT/AOT build choice, polling, thread counts, KV dtype, MTP draft settings where available, and model-specific feature flags.
  5. If a candidate appears within the noise band, run same-window repeats across multiple GPUs and compare to a control. Do not declare sub-1% wins from a single run.
  6. Promote only after the strict realistic suite passes with all cached tokens zero.
  7. Write a result packet under results/rapid-model-snapshots-b70/<model>/, a repro command/script when useful, and a LocalMaxxing queue entry only for strict-valid rows.

Storage Rules

Result Ledger

Use results/rapid-model-snapshots-b70/README.md for promoted or useful final snapshots. Use this experiment folder for active notes, failed ideas, and diagnostic-only screens.

Current promoted rapid rows:

Helpers