Logging this as an idea discussed with GitGab, but would be cool if SV2 UI had some sort of mini benchmark build it, either through leveraging stratum-benchmark or something simpler.
Basically users these days are faced with plenty of pools. For Solo pools for example, aside from fee structure it may be difficult for a miner to understand what's the "best" pool for them. For pool mining, I assume we'll reach a similar point as more pools are added, it may be cool to have an optional "benchmark tab" that would allow user to run a pool for a defined amount of time, then we fallback to another, and once it's done for all pools or the ones selected we can showcase benchmark page.
This is crazy idea not immediately to be prioritized!
I think it should be much simpler version of our benchmarking tool, some metrics that could be measured:
- Latency
- Share rejection (def impacted by latency)
- Any other?
Logging this as an idea discussed with GitGab, but would be cool if SV2 UI had some sort of mini benchmark build it, either through leveraging stratum-benchmark or something simpler.
Basically users these days are faced with plenty of pools. For Solo pools for example, aside from fee structure it may be difficult for a miner to understand what's the "best" pool for them. For pool mining, I assume we'll reach a similar point as more pools are added, it may be cool to have an optional "benchmark tab" that would allow user to run a pool for a defined amount of time, then we fallback to another, and once it's done for all pools or the ones selected we can showcase benchmark page.
This is crazy idea not immediately to be prioritized!
I think it should be much simpler version of our benchmarking tool, some metrics that could be measured: