Repository navigation
docs: the README's All in one numbers, and why the memory offset differs from run to run - #34
Merged
Merged
Conversation
…rdware check 94 Three runs on one day applied +650, +1600 and +550. The two logged scans show the bandwidth rising in a straight line to +2450 and the first wrong result at +2550: there is no peak before the errors on this card, and the scan ends where two readings in a row happen to fall 1 % under a high one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e check 94 5309 to 5353 it/s, 185 to 166 W, fans 70 to 52 %, in 31 minutes, with v0.4.6. The two earlier runs are named next to it; the screenshot is of the first of them and says so. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Documentation only.
The README's numbers
The All in one section and the picture at the top (
hero.svg) now carry the run of hardware check 94, made with v0.4.6 on the reference RTX 4070: 5309 to 5353 it/s (+0.8 %), 185 to 166 W (-10.3 %), fans 70 to 52 %, in 31 minutes. The two earlier runs are named next to it. The screenshot of the result screen is still of the first of those and says so.The memory offset
Three runs on one day applied +650, +1600 and +550 MHz on that card. The two logged scans show why: the bandwidth rises in a straight line to +2450 MHz and the first wrong result comes at +2550, so there is no peak before the errors, and the scan ends where two readings in a row happen to fall 1 % under a high one. Recorded at hardware check 94 and as an open point in
docs/development.md. Nothing in the search is changed.🤖 Generated with Claude Code