Repository navigation
perf: measured NumPy table at v0.41.0 on one Zen 3 core - #119
Merged
Merged
Conversation
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.
This is the first measured
docs/perf.json/docs/perf-table.md. The table had been "deferred" since the harness landed (Refs #105), because the development host's load was above the gate of 8. The figures are on #118.de3f41ac4ec1e21554a63f95e4041143acfd58bd, clean. The table's Commit line shows no-dirty.taskset -c 9,GOMAXPROCS=1, Go 1.27.4.uvfrombench/refs.txt.bench/gave the same verdicts, stamped…-dirty, and was discarded.docs/perf.md: the Status section now describes the measured table, and the harness is named refbench v0.3.0.A refbench behaviour hit on the way, to report to go-scikit/refbench:
-perf.run(load gate tripped) writesdocs/perf.jsoninto the clone.-perf.resumethen sees the tree as dirty.-perf.commit <tag>refuses a dirty tree.A partial run therefore cannot be resumed, and a fresh
-perf.run -perf.onload=waitwas the way through.Refs #118
🤖 Generated with Claude Code