Post
Topic
Board Mining (Altcoins)
Re: [ANN] Bminer: a fast Equihash miner for CUDA GPUs (6.0.0)
by
gettilee
on 24/03/2018, 19:47:49 UTC
I am not an expert neither pro Bminer, but your test or asumption is vague. You barely ran Bminer for a couple of hours and the comparason is not fair. It should be made with both miners running at the same time in different machines with exacty the same hardware and settings to have exactly the same conditions.

I do agree the invalid share rate is a bit higher. I have just started using Bminer as a try out and I have noticed exactly the same but can´t say is fair either because I am not running both miners at the same time.

With DSTM I use to get 0,2% rejected shares and with Bminer so far is nearly 0,5% but I have only been running it for the past 12 hours and been playing with the windows energy management to cut down the CPU.

This is my performance with 6 GTX 1070 Ti, 70% TDP, +200 clock, +700 memory:
https://imgur.com/aJcqJea

And this is Flypool:
https://imgur.com/o8FdH8l

There are more fluctuations with Bminer so far, but as I said I have only used the miner for the past 12 hours and I´ve playing with the CPU energy to cut down so more Watts so It will need another 24 to 48 hours to be stable on the pool. I´ll post again the results in 24 hours

my post wasn't claiming any kind of test. i simply showed how many invalid shares bminer 6.0 was producing in just a few hours compared to dstm which was  running with considerably less over a longer period of time.

i was curious to see what "improvements" bminer had with this latest build and i don't see any hashrate improvement for 1070ti's nor do i see a drop in invalid shares.

i've ran tests before on bminer vs dstm on the same pool at the same time with the same hardware. bminer has always had more invalid shares than dstm.
bminer also over reports hashrate by 3% on console that is not reflected in the pool. combine that with the private connection...either bminer is lying about the console reported hashrate or that hes taking more than 2% because the pool (flypool for my tests) does not reflect the 3% console gain over dstm.