docs(readme): add local apples-to-apples rez 3.3.0 benchmark#74
Merged
Conversation
The previous "Status / Fast" bullet quoted "~44 s vs ~206 s" from an older state of the code. The `rez_benchmark_dataset` example's inline "rer is Nx rez" was comparing local rer to rez's published 2022 benchmark artifact recorded on a 2-core Azure VM — different hardware, different rez version, not directly comparable. Run rez 3.3.0 (vendored as the submodule we already have) locally on the same machine that produces the rer numbers, capture both runs in the README: machine: Intel Xeon E5-2699 v4 @ 2.20 GHz, 32 cores, Linux 5.14.0 rez 3.3.0: 405.17 s (mean 2 152 ms, median 1 162 ms) rer 0.1.0-rc.6: 11.35 s (mean 60 ms, median 30 ms) speedup ≈ 35.7× on total, 39.3× on median Includes a "How to reproduce" block (the rez side is just `pip install ./rez` + `rez-benchmark`), and pointer to the published 2022 artifact as historical context with an explicit "not directly comparable" note. Also reframe the "Validated 1:1" status line to reflect what the differential test actually checks (solve status + (name, version) set), which doesn't currently enforce variant-index parity. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
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.
Summary
Replaces the old "rer is Nx rez" claims (which compared local rer against rez's 2022 published artifact on a 2-core Azure VM — different hardware, different version, not apples-to-apples) with a fresh run of rez 3.3.0 + rer on the same machine.
Local results
```
machine: Intel Xeon E5-2699 v4 @ 2.20 GHz, 32 cores, Linux 5.14.0, Python 3.9.25
```
Both run on the same workload from `rez/src/rez/data/benchmarking/`, default solver config, single core. `rer` solved 187/188 with the same `(name, version)` set as rez; the one failed request fails on both sides.
What changed in the README
fam_requires#68, perf(resolver): intern package family names asRc<str>#70, perf(resolver): O(1)extractable()via length compare #71, perf(resolver): track per-scopeextractablestate at phase level #72, perf(version): wrapRangesinRcinsideVersionRange#73).Verification
🤖 Generated with Claude Code