Post
Topic
Board Mining (Altcoins)
Re: [ANN] Bminer: a fast Equihash miner for CUDA GPUs (5.3.0)
by
resiva
on 07/02/2018, 17:39:24 UTC
On ethermine pool I can tell you that it has always under reported my estimated payment and hashrate, but the _actual_ payment matched almost exactly what I expected. It may be that something is off on their side ... but as long as it's off in the same way for all miners then your test is relevant (for which miner's best).

If you want to compare payouts, then leave it longer than 24h (say, 3 days?) and after you stop the rigs, allow for at least 1h more so that the last shares you mined get counted in the last 1h window on Flypool.

I secretly hope bminer is better in the end, simply because dstm on my rigs is reducing hashrate due to too much cpu hogging.

Unfortunately, my connection to flypool goes down and all four rigs stop working at the same time around 13:30. Here is the summary of tests I have for the 12 hours, you can check on the page:

dstm: https://zcash.flypool.org/miners/t1SstC4pJy3JtKdqSoFJZk6SUtyznfo1ZB6
https://i.imgur.com/g7agrmg.png

bminer : https://zcash.flypool.org/miners/t1LLJPAoYajZjPQggPZcdDpwPont4AoGvfq
https://i.imgur.com/sjcIHk9.png

              Pool avg. hashrate          Payout
dstm               5.29kH               0.03619ZEC      
bminer            5.48kH               0.03847ZEC

If you are interested in seeing the full running logs, here it is: https://ufile.io/f2906

Note that my experiments should NOT be interpreted as a general experiment that can apply to all situations. The best way to find out which miners work best for you is to try it yourself.

To be honest, I see this as a healthy situation for all of us. As long as the difference between bminer and dstm is small, they will have to play fairly (for example, not raising devfees) and we get more choices.

If I have time, I may run a comparison again maybe on another pool. But I cannot promise because doing this takes a lot of energy.


That's very strange.
On my tests dstm constantly outperforms bminer on pool side.
It's even more strange since bminer reports localy a higher hash rate.

However my main concern is the private connection of this miner.
The dev can increase / decrease the fee anytime he want's.
Downgrading won't help us because of the private connection.
Actually he can do what ever he wants, that's why he put the private connection in, I'm pretty sure about this.
Supporting this kind of miners seems to be a very stupid thing for us to do - there is no other miner I'm aware of which requires a private connection - this miner requires a private connection to even start mining.