Skip to content

vision-suite: 0.35.0 on the H100 — the campaign, the 908 gate on Hopper, OCRBench and MLX-CUDA gemma4 budgets - #459

Merged
glennneuber merged 4 commits into
mainfrom
vision-suite/campaign-2026-10-04-h100
Oct 5, 2026
Merged

glennneuber merged 4 commits into
mainfrom
vision-suite/campaign-2026-10-04-h100

Conversation

@glennneuber

Copy link
Copy Markdown

In short

  • 0.35.0 changes nothing on the H100.
    • GGUF output is identical to 0.34.4's in all 84 campaign arms and all 3,000 OCRBench answers.
    • MLX moves no more than 0.34.4 moves against itself.
    • OCRBench scores repeat, except qwen3.6 at 877 against 878.
  • Keep 908. On Hopper too, llama.cpp's own tiling leaves more gemma4:26b-a4b think-on cases in loops that never
    end: 4 of 27 without 908, 1 with it. The sm_120 host gave 6 and 1. Both arms reproduced byte for byte on a second
    run.
  • gemma4:31b-it-q4_K_M's prefill drift is not the build, the prompt cache or the serving path. Every
    configuration measures the same prefill today, so 2026-09-30's figure stays unexplained.
  • The prompt cache costs time outside the prefill timer: about 4 % per campaign cell, and 21 % per OCRBench item
    on gemma4:31b-it-q4_K_M.
  • MLX-CUDA clamps gemma4's image budgets to 70–1120, read from behaviour. budgets_observed stays false.

What's in it

  • New:
    • docs/maxusai/vision-campaign-2026-10-04-h100-sm90.md;
    • its bundle (35 cells), host profile and budget readings under vision-suite/bench-runs/.
  • OCRBench:
    • eight new arms (bench-runs/ocrbench/ext_h0350-*) and their host profile;
    • a 2026-10-04 section in ocrbench-h100.md;
    • a note in ocrbench.md.
  • Records:
    • The v0.35.0 fold record gains the H100's gates 4–6 and its deploy. Its preflight-profile table now reflects preflight: CUDA profiles admit 0.35.0; payload pins on native Linux #444.
    • The 908 register row gets the sm_90 measurement.
    • llama-server-prompt-cache.md and the 2026-09-30 campaign document point to the new evidence.
    • [expect.mlx-cuda.gemma4] gets a dated comment. No value changes.

Checks

  • Every table renders verbatim from committed data, with summarize_engine_compare.py --bundle and
    summarize_extbench.py. The derived counts come from snippets in the documents that read only committed files.
  • Local runs pass: test_verdicts.py (238 OK), test_bundle_campaign.py, test_summarizers.py,
    test_extbench.py and check_source_paths.py. The no-names check needs CI's deny-list.
  • The data was scanned for hostnames, home paths, IDs and emails. The only hit is an email address printed in an
    OCRBench test image, already in the 2026-10-01 files.

Not in it

  • No code, and no new scripts.
  • The runs' logs, raw responses and thinking traces stay outside the repo. The VM they ran on is deleted on
    2026-10-07.

🤖 Generated with Claude Code

glennneuber and others added 4 commits October 5, 2026 15:11
…e 908 gate on Hopper and think-on across the fleet

The 2026-09-30 campaign again on 0.35.0-dynres-15-ga657392, the build the H100's
production service runs, on a second server of it. Think off, all 84 GGUF arms equal
0.34.4's, and MLX moves no more than 0.34.4 moved against itself. Think on, seven tags:
no GGUF case loops. The 908 gate on sm_90: 1 of 27 gemma4:26b-a4b cases loops with 908
and 4 without, each arm run twice with byte-identical results. gemma4:31b-it-q4_K_M's
prefill drift is not the build, the prompt cache or the serving path. MLX-CUDA clamps
gemma4 image budgets to 70-1120.

The bundle holds all 35 cells; the 2026-09-30 document now points to the prefill answer.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…mpt cache off

All 1000 items for the eight campaign tags. Seven scores equal 2026-10-01's and
qwen3.6:35b-a3b-nvfp4 scores 877 against 878. The three GGUF arms give every answer
byte for byte and run 21 % (gemma4:31b-it-q4_K_M) and 8 % (qwen3.8:27b-q4_K_M) faster
per item, the prompt cache's cost.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…budgets read from behaviour

- The v0.35.0 fold record gains the H100 as a host: a Go-only build of main on
  production's payload, #444's preflight, this campaign as gate 6, and the deploy. Its
  profile table no longer says CUDA admits no 0.35.0 profile.
- The 908 register row records the sm_90 measurement: the condition is met on neither
  architecture.
- The prompt-cache document records that the suite's prefill timings leave the cache
  update out, now measured, and OCRBench's speed-up with it off.
- [expect.mlx-cuda.gemma4] records the budgets read from behaviour. budgets_observed
  stays false: no load log shows them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… answers, and which server ran the 0.34.4 cells

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@glennneuber
glennneuber merged commit 5273e49 into main Oct 5, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant