What is an acceptable Rejection Ratio for Braiins Hashpower? I’m running Knots and Datum gateway on an RPi4 and would like to make sure it’s not causing a bottleneck. Below is a screenshot of the rejection ratio I’m referring to.
0.09 is very low. I wouldn’t worry.
What would be considered too high or problematic? I’m assuming that the rejection ratio can also be seen as a loss in revenue of that percentage since that would otherwise be shares associated with your mining in the pool. In other words, if the rejection ratio is 0.09% then your pool earnings will be 0.09% less. So I guess, a bad rejection ratio would be whatever amount of loss you’re willing to absorb.
Occasional rejections are normal. Even my local miners have errors. All are usually under 0.10% to maybe 0.15%
Things like the following could effect rejections:
- Stale Shares - High network latency or long submit time
- low difficulty / outdated target — Pool adjusted difficulty
- Invalid nonce / hardware errors
Sustained high rejection rate of >1%-2% will effect earnings much more then the small percentages of just regular ole mining. The highest I’ve seen from Braiins (48 orders) is like 0.48% and that ordered auto cancelled. The rest run at 0.09%-0.21% which I consider normal as compared to my own home miners.
There is no way you can really control shares from Braiins (from my experience) anyways unless the VPN or remote stratum port (hashGG) your using is the culprit. If that happens I imagine you just have to find better routing.
Braiins dumped the order:
1 Like