Topic: [ANN]Bminer: a fast Equihash/Ethash/Cuckaroo29z miner for AMD/NVIDIA GPUs 16.4.9 - page 98. (Read 148347 times)

@realbminer: when 144,5?

Thanks for your nice work on the miner!

can u guys pls compare to this miner vs. ccminer and other eth miner ?

yay waiting 144,5 and 192,7 version

thank everybody . it is useful.

BTCZ is going to fork tomorrow
Safecoin is going to fork this weekend
EWBF released his Zhash miner

As i like your stable miner, a ZHash-Bminer would be really nice

Dear community:

We realized that there are ASIC miner or ASIC miner monitor named BMiner/Bminer.
Just want to inform that it has no any relation to our business.

Bminer is a highly optimized cryptocurrency miner that runs on modern NVIDIA GPUs.
Our only official website is www.bminer.me
Please check this website to catch up all Bminer related information such as history versions, download links, new business other than any other way.

Best,

realbminer

I actually thought and posted the rejected shares had improved but I think it is not the case. Please realbminer have a look at this:

Miner it’s been running since 11:20 non stop and has reported only 10 rejected shares pretty much in 1370 so that’s 0.73% rejected shares.


But flypool server reports far more rejected shares than your miner does in the console. I actually has reported 30 rejected shares vs 10 on the miner console. If we use that figure is 2.19% rejected share.


How is that possible? It’s 200% more rejected shares on the pool that in the miner itself.

Thanks

count the green bars at the bottom of the picture you will get 20 small green bars and 5 double green bars. Single green are one rejected share and the double are 2 rejected share. Those are the 30 rejected shares
[/quote]

Hi Keko Fdez：

Sorry for the late reply.
your problem didn't re-appear on my rig but I want to explain that there are several reasons may cause rejected shares.
such as Overclocking and Network latency.
If your latency to the pool is too long, then a valid share may become stale and invalid during the transmission. This will cause the share being rejected. The solution to this problem is to choose a pool server that has low latency connection to your rig.

Please see: https://www.bminer.me/faq/#why-i-see-rejected-shares-when-using-bminer

another user mentioned to me the same problem and after a couple of reboot the problem was solved.
does this still happen to you? would you please also try this command to see if it helps?
Set -gpucheck to 0 could skip the gpu check.

Hi, fabry1999 Thanks for the feedback.
Set -gpucheck to 0 could skip the gpu check. is this command what you need?

What coins do you mine now? maybe you can share some experience with the community here and give Bminer team some idea about what coins should we support in Bminer.
also, it's a good point about the constant rate. I mean the rate may vary on different rigs. I will take a look at this problem as well.
then about the rejected shares, how many hours did you do the test?

It's sweet!
I really appreciate Keko Fdez and supermoew for testing and give me feedbacks to make Bminer better.
I also appreciate your way resoving misunderstandings.
it's nice to have you guys with Bminer community.

I wouldn’t say is not fixed. The problem is that you have to take off the 2% dev fee plus the 1% pool fee from the hashrate in the console to get the real one and still the hashrate in the pool is estimated based on your shares so not really accurate either.

For me the reason of not using it is because with DSTM I get less rejected shares and a more constant rate on the pool like pretty much a straight line whilst with Bminer is like a roller coaster jumping all over the place.

As I said before there are more profitable coins out there so not mining ZEC anymore unless the price goes up again  

Hi xxxyyyzzz, thanks for the feedback.

Firstly we have explained how Bminer reports hashrate and how pools reported hashrate here: https://www.bminer.me/faq/
Bminer reports hashrate generated by your hardware, while a mining pool estimates the hashrate based on the number of submitted shares.
The Bminer hashrate is different from the pool hashrate because:
1.The Bminer reported hashrate includes the devfee.
2.A small portion of the generated shares may get rejected or become stale due to network delay and transmission problems. Bminer reported hashrate will include such shares, but such shares will not contribute to the pool estimated hashrate.
3.Your pool hashrate is an estimate based on received shares, therefore it will vary a lot unless you control a significant amount of hashpower and you run it over a long period of time.
4. Some pools may calculate the estimated hashrate incorrectly.

Secondly, if you want to have a conclusion that which software is faster, please make sure using the same mining rig, same mining pool and run it over a long period of time, otherwise your conclusion may be wrong.
So may I ask how many hours you running the test of Bminer and if you have made the same test with other mining software.
you can paste your rig information and test result in the pool if you did.
there are youtuber test in the video you can watch:
https://www.youtube.com/watch?v=_laCFKg-HRg&t=31s

Thirdly, we don't inflate the hashrate for attracting users. But since you are reporting this as a problem, I will take a look into this it to see what I can do to make it better again.

Thanks for your feedback again!

no, problem.

anyway, has anyone compared bminer and DSTM, and EWBF lately  ...on poll side of course...  really annoying is that bminer showing 5-10% bigger hashrate  on console that is on pool ( tested and discussion made a lot but that was older versions not v8). 
i' better prefer to show real thing.. so i can easily compare what is faster for my rig.   i mean i can understand that maybe at first it inflate hashrate to make people using it, but now when we all know what is it.. it will be better to fix console to real hashrate...

No need, no harm made

Then I apologize to you. I just saw realbminer's posts.

First of all I don´t blame the miner I comment about it and my performance with it so it can be improved which is something different like the post I did a couple of days ago about the rejected shares that you were not able to see and commented back. Hope you were able to see the green lines by now because realbminer did and is trying to look at it.

Second I can´t say anything about ewbf because I have never used that miner, always used DSTM miner and it has always been faster for me not on the console were Bminer is faster but on the pool side with more constant hashrate and less rejected shares. So I can only talk about what I have used that is why you never see me talking about ewbf.

And finally, like many others I don´t give a shit about one miner or another don´t support any of them in particular don´t know the developers not friends why them so I just use the most convenient for me for what I want to get and like right now not using neither Bminer nor DSTM. Gave up on mining ZEC because the profit has drop like hell to 4.12 dollars/day for my rig and there are more coins out there to make bigger profits

My mistake then, Post looked exactly similar anyway I apologise

BTCZ community is going to do a hard forking to equihash 144,5 on June 15, really excited to see this move.
https://kryptocal.com/event/21529/zhash-forking

What I feel suspicious is that why you blame this miner other than ewbf ...
I just checked your latest posts and you keep complaining about this miner is slower in mining equihash and no one else ever mentioned....