Repository navigation
bench: real-world tree shapes, named after what they are - #36
Merged
Merged
Conversation
|
Bencher Report| Project | remmy |
| Branch | pr-36 |
| Testbed | vultr-bare-metal |
⚠️ WARNING: No Threshold found!Without a Threshold, no Alerts will ever be generated.
- Throughput (operations / second (ops/s))
- Latency (nanoseconds (ns))
- time-ratio-vs-main (Measure (units))
Click here to create a new Threshold
For more information, see the Threshold documentation.
To only post results if a Threshold exists, set the--ci-only-thresholdsflag.
Click to view all benchmark results
| Benchmark | Latency | milliseconds (ms) | Throughput | operations / second (ops/s) x 1e3 | time-ratio | Measure (units) | time-ratio-vs-main | Measure (units) |
|---|---|---|---|---|---|---|---|---|
| demo/balanced-38k/warm/main@1 | 📈 view plot | 612.71 ms | 📈 view plot | 62.39 ops/s x 1e3 | 📈 view plot 🚷 view threshold | 0.95 units | ||
| demo/balanced-38k/warm/main@4 | 📈 view plot | 212.74 ms | 📈 view plot | 179.69 ops/s x 1e3 | 📈 view plot 🚷 view threshold | 0.33 units | ||
| demo/balanced-38k/warm/remmy@1 | 📈 view plot | 613.24 ms | 📈 view plot | 62.34 ops/s x 1e3 | 📈 view plot 🚷 view threshold | 0.95 units | 📈 view plot | 1.00 units |
| demo/balanced-38k/warm/remmy@4 | 📈 view plot | 213.11 ms | 📈 view plot | 179.37 ops/s x 1e3 | 📈 view plot 🚷 view threshold | 0.33 units | 📈 view plot | 1.00 units |
| demo/balanced-38k/warm/rm@1 | 📈 view plot | 645.65 ms | 📈 view plot | 59.21 ops/s x 1e3 | ||||
| demo/balanced-38k/warm/xargs@1 | 📈 view plot | 879.22 ms | 📈 view plot | 43.48 ops/s x 1e3 | ||||
| demo/balanced-38k/warm/xargs@4 | 📈 view plot | 423.26 ms | 📈 view plot | 90.32 ops/s x 1e3 |
3 of 4 tasks
F0..F7 said nothing: reading a result meant looking the id up in registry.py. Each id now names the tree's shape and file count (balanced-58k, wide-51k, deep-58k, balanced-58k-4kib, large-1mib-files, tiny-125, balanced-333k, flat-58k). That's what pytest ids, chart file names and Bencher benchmarks show: demo/balanced-58k/warm/remmy@4. A test keeps each id's file count in step with its tree. Trees, tools, sampling and the decision rule are unchanged.
markovejnovic
force-pushed
the
bench/fixture-names
branch
from
September 28, 2026 09:21
508e979 to
74255ef
Compare
The anchor (585 dirs x 100 empty files) was mktree's defaults, with no source for calling it typical. Measured eight real node_modules trees (express to bitwarden/clients): every one has ~7-10 files per dir, not 100, and ~80% of files are <= 4 KiB, so each frees one block; none are empty. The anchor is now vscode's shape made uniform: fanout 4, depth 6, 7 files per dir (5,461 dirs, 38,227 files; vscode c17dab9 has 5,538 and 39,966). Every small-file tree uses 4 KiB files. The trees that vary one thing of the anchor follow it: wide-38k keeps its dirs and files at one level, flat-38k its file count in one dir, deep-36k a similar count. The huge tree is the anchor one level deeper (152k files, monorepo sized) instead of 333k, which at 4 KiB would write 1.3 GB per run. balanced-58k-4kib is gone: the anchor is that now.
markovejnovic
changed the title
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
1 participant
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.
No description provided.