ci: bench against latest release, measure memory consumption and executable size#2177
Merged
Merged
Conversation
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
0b913d9 to
f41341f
Compare
ArthurZucker
approved these changes
Jul 10, 2026
- remove the FIXTURE_BENCH_* env-var overrides (nothing used them) - drop the `supported` JSON field: no consumer left — the renderer keys off `results`, the CI gate off `ids_match` - binsize_svg: remove the dead not-measured/None paths (the workflow always writes both keys or fails) and an orphaned column header - mem_line: drop the dead guard — only benched models reach it - fix stale docs: no latency measurement exists, no `stub` binary size - replace the boxed encode closure with a plain Option<closure> Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
f936f0b to
ecee316
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PipelineTokenizer benchmark
5 / 6 models supported — PipelineTokenizer vs
tokenizersv0.23.1 (latest release) · ~10 kB inputs · single threadf41341f18 · 2026-07-09 18:57 UTC· Intel(R) Xeon(R) Platinum 8375C CPU @ 2.90GHz · 16 coresbert-base-uncased — normalizer-heavy WordPiece · ×4.28 vs v0.23.1
Memory (RSS MB, load+encode): v0.23.1 2+0 (peak 6) · Pipeline 5+0 (peak 6)
deepseek-v4 — split-heavy byte-level BPE, 3 chained regexes · ×2.66 vs v0.23.1
Memory (RSS MB, load+encode): v0.23.1 51+0 (peak 58) · Pipeline 84+0 (peak 84)
gpt2 — standalone ByteLevel pre-tokenizer · ×7.91 vs v0.23.1
Memory (RSS MB, load+encode): v0.23.1 17+1 (peak 18) · Pipeline 21+0 (peak 21)
llama-2 — model-bounded BPE, no pre-tokenizer · ×3.04 vs v0.23.1
Memory (RSS MB, load+encode): v0.23.1 15+0 (peak 15) · Pipeline 14+0 (peak 14)
llama-3 — split-heavy byte-level BPE, single regex · ×4.06 vs v0.23.1
Memory (RSS MB, load+encode): v0.23.1 128+0 (peak 189) · Pipeline 129+0 (peak 189)
Not yet supported:
t5-base