Add experimental benchmarking to SV2 UI - #229
Open
pavlenex wants to merge 13 commits into
Open
Conversation
Co-authored-by: Pavlenex <36959754+pavlenex@users.noreply.github.com> Signed-off-by: Pavlenex <36959754+pavlenex@users.noreply.github.com>
Add block-found, best-difficulty, and pool-failover defaults, bot command controls, and monitoring-backed alert detection. Co-authored-by: Pavlenex <36959754+pavlenex@users.noreply.github.com> Signed-off-by: Pavlenex <36959754+pavlenex@users.noreply.github.com>
Add backend-owned pool rotation, latency and share measurements, configuration restoration, ranked results, and start-mining actions. Co-authored-by: Pavlenex <36959754+pavlenex@users.noreply.github.com> Signed-off-by: Pavlenex <36959754+pavlenex@users.noreply.github.com>
Co-authored-by: Pavlenex <36959754+pavlenex@users.noreply.github.com> Signed-off-by: Pavlenex <36959754+pavlenex@users.noreply.github.com>
Co-authored-by: Pavlenex <36959754+pavlenex@users.noreply.github.com> Signed-off-by: Pavlenex <36959754+pavlenex@users.noreply.github.com>
Cap and spread latency sampling, reject partial-success rankings, retain per-channel share totals across reconnects, and clarify the benchmark's limits. Co-authored-by: Pavlenex <36959754+pavlenex@users.noreply.github.com> Signed-off-by: Pavlenex <36959754+pavlenex@users.noreply.github.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
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 PR follows the approach in #228 and builds on top of it, adding highly experimental Benchmarking feature. The user goes to settings > experimental, enables benchmarking and then tab appears. Based on users initial configuration (I only tested with solo pools) at least two pools are needed to be able to benchmark and user can define time frame, once timeframe expires we fallback to another pool to benchmark.
Pool benchmarking is designed to help users identify which pools work best from their location and with their specific mining setup. It tests each selected pool for the same duration and compares average TCP connection time, SV2 setup time, and accepted and rejected shares.
The attached video shows a short test with only one minute allocated to each pool. These results are not intended to represent or showcase the overall performance of any pool.
benchmark-sv2-experimental.mp4
This is a rough proof of concept, and it would be valuable to discuss which metrics are genuinely useful and how they should be measured and presented to provide fair, meaningful comparisons.