Faster hashrate display updates #196
Merged
Conversation
This file contains 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.
On pools like OCEAN with a relatively high minimum difficulty, the bitaxe wasn't updating the hashrate often enough.
Changed the hashrate updates to happen on every chip share as opposed to every pool share.
This calculation relies on the share difficulty threshold, so I had to move that from pool diff to chip diff (called ticket in some places). It seems with the BM1366 and the BM1368 we have that fixed at 256. If we ever decide to make that dynamic in the future, this hashrate calculation will also need to take that into account.