[ANN]Bminer: a fast Equihash/Ethash/Cuckaroo29z miner for AMD/NVIDIA GPUs 16.4.9

[stash2coin]

Network difficulty is constantly changing , so in order to make accurate measurements you have to test with both miners working at the same time

[MSV]

Network difficulty is constantly changing , so in order to make accurate measurements you have to test with both miners working at the same time

Thank you for the reply. I'll maybe try another test sometime on 2 same cards/systems at the same time.

I'd like to prove Bminer is more profitable than DSTM. Has anyone done enough tests to conclude this to be the case or not?

[eniacs]

Using Bminer for 3 rigs here. Good hash rate, better than any others I've tried. Although as others have noted, not as stable and uses a lot of CPU.

Somtimes even crashes on "GPU hang" but running a EWBF miner works fine...

Anyway question;

Can you select only certain GPU's on BMiner?

[Bimmber]

How do I install bminer on ethos 

[snitsaruk]

Changing from EWBF to DSTM increased average Sols from 520 to 534. Number of shares increased from 167 to 180 over a 40 minute test period on both. I then tried Bminer. For another 40 minute test, sols increased to 550, however the number of shares reduced to 147. There were 0 rejected shares on all 3 tests and same 1070ti, same overclock, same pool and exactly 40 min.

Very impressive higher sols with Bminer but how come the number of shares would be less than EWBF and DSTM?

I can confirm the fact that the indicators of the miner and the pool do not match.
For the purity of the experiment, I disabled the author's commission on Bminer by specifying the option "-nofee".
8 ASUS GeForce GTX1070 8192Mb DUAL (DUAL-GTX1070-8G) video cards show the value 3930 Sol in the miner, and on zcash.flypool.org 3520 Sol.
The difference is 410 Sol. The Bminer test lasted 30 days. A total of 64 video adapters participated in the test.
On average, for 30 days Bminer showed a better result than EWBF by 0.3%. In EWBF, the commission was disabled by the option "--fee 0".
Perhaps Bminer will show better results on video cards nvidia 1060 or nvidia 1050 Ti, but for nvida 1070 the difference is very insignificant only 0.3%
I want to clarify that on all video cards PowerLimit has been downgraded.
The average value on the core was 925 mV.

P.S.
A big plus is that you can write logs to a file. Previously, Bminer did not have such an opportunity.
I hope that the author will correct the code of the miner so that the indicators on the screen and in the pool are the same. Because of different indicators, a sense of deception arises.

Perhaps someone this information will be useful.

[haitran]

Changing from EWBF to DSTM increased average Sols from 520 to 534. Number of shares increased from 167 to 180 over a 40 minute test period on both. I then tried Bminer. For another 40 minute test, sols increased to 550, however the number of shares reduced to 147. There were 0 rejected shares on all 3 tests and same 1070ti, same overclock, same pool and exactly 40 min.

Very impressive higher sols with Bminer but how come the number of shares would be less than EWBF and DSTM?

I am testing with my rig 10x 1060 over 36h and I want to run already 48h for confirming that many miners have claimed bminer notices over hashrate.

Not the number of shares reduced but there are too many reject shares and it increases reject shares more and more as your rig runs hour by hour, day by day. You can track your console when miner runs, it has just 0 reject share when start, after an hour It has 1 or 2 reject shares, and it gets more and non release by rounds. My rig runs for 6 hours with 7 and 9 hours with 10 reject shares. The reject shares only return to 0 when you reload your bminer. If It gets more and I have to switch back to dstm for the real thing that we see we get...

I think the problem is just there are too many reject shares, so the efficiency is no more than others. Every other thing works fine.

[stash2coin]

Currently i'm having 6402 accepted and 24 rejected for 21 hour period, you can do the math to see percentage wise. But i dont see higher rejected shares than other miners software. Could be many other problems that can contribute to high reject shares not only the mining software!

[Elisaly]

after 40 pages

no one can confirm the ability of Bminer so i rolled back to DSTM

[frequencydip]

5.3 crashes on my rigs constantly. I have tried on both Fedora and CentOS backed rigs. It does run about 10% faster but the lack of stability makes it a net loss.

[unique83]

I started my own test between BMiner and DSTM. I am using one 1070 on each miner.
Bminer is running on GPU0 and is reporting 470 - 475 Sol/s so i would say the average is around 472. Dev fee is on.
DSTM is running on GPU1 and is reporting an average of 452.3 Sol/s.
I will run this for 24 hours and then i will switch GPU's so that GPU0 runs DSTM and GPU1 runs BMiner, so the test will run for a total of 48 hours.
The reason for this is because GPU0 seems to run on slightly higher core clock even when OC is synced (i have identical cards). 
For now it looks like DSTM is in the lead.
If anyone is interested in results you can follow them here:
DSTM: https://zcash.flypool.org/miners/t1JpfnPhfeuGonSvCSX27vVq8aiSsqVSxgi
BMiner: https://zcash.flypool.org/miners/t1cJjfbrtXTWNV3NMVhF7s8LUTNmrU6iLW8

I will post an update after 24 and 48 hours.

[Andrey09]

You shoud have same clock in Afterburner for both cards for better test.

[unique83]

This is why i will switch miners on each card after 24 hours.

[almartins]

Hi,

It seems that after 24 hours the result is the same = Unpaid Balance + Immature Balance.

But what about energy consumption?
For me (1080) Bminer is inferior to DSTM and for you?

[unique83]

It will be 24h in 7 hours from now.
Also it should be noted that currently bminer is running on a slightly faster card so this slight advantage for bminer is expected. Earnings are pretty close at this time, but true results will be after 48h.
As for energy consumption...my wattmeter shows the same values for both miners.

[ltc_bilic]

@realbminer

Today there was a problem with the zenmine.pro mining pool,...don't know what was up but after investigating I've found out that bminer still has some sort of connection problems...see the picture below,...all this time the GPU was at full load,...although it didn't had a proper connection to the pool and I couldn't see it on the minning pool. Then I've switched to ewbf/dstm, both miners connected immediately and are working properly?

I use following in a batch file:

-max-temperature 80 -max-network-failures 5 -gpucheck 0 -watchdog=false

I've tried without SSL connection to the pool, and the result was the same. Everything that's written in a console is written also in a log file,...so nothing new can be obtained from the log file.



This is a huge issue! I've lost at least half of the hashrate because of this bug.

[lankyman]

Bminer is a highly optimized Equihash miner that runs on modern NVIDIA GPUs (Maxwell and Pascal, i.e. GPUs that have compute capability 5.0 or above). Bminer is the fastest publicly available Equihash miners today. It features a completely restructured algorithm to maximize the stream processor occupancy and the instruction pipeline efficiency. It realizes the full potentials of Pascal GPU cards.

Bminer also comes with REST APIs to facilitate production deployments (e.g., mining farms).

Similar to other miners, Bminer contains 2% devfee.

Features

Fast

• 735-745 Sol/s on GTX 1080Ti
• 450-460 Sol/s on GTX 1070
• 315-325 Sol/s on GTX 1060
• On stock settings

Secure and reliable

• SSL support
• Automatic reconnects to recover from transient network failures
• Automatic restarts if GPUs hang

Operation friendly

• Comes with REST APIs to facilitate production deployments

Quickstart

To mine Zcash on nanopool:

• Download and extract Bminer into a folder (e.g. C:\bminer or /home/bminer)
• Edit mine.bat (mine.sh on Linux) and change the address to the desired Zcash address that Bminer mines towards.
• Open command line prompt and run mine.bat (mine.sh).
• Enjoy mining  

Please see https://www.bminer.me for advanced usages, APIs and updates.

Downloads

• Linux x64: bminer-v5.3.0-e337b9a-amd64.tar.xz
• SHA256 checksum: 6e742df803a99dfdb4505890344b21968185081e99b10a8cfc312886bce131be
• Windows x64: bminer-v5.3.0-e337b9a-amd64.zip
• SHA256 Checksum: 3b7476d7f71f85a1fcdc97f5f283bdb457aca152b4041388a76ca02a4d7654ff

Release notes


5.3.0

• Experimental support for EthOS / Ubuntu 14.04.
• Support AMD K10 CPUs.
• Automatically restart hanged network connections.
• Improve compatibilities with mining rigs with more than 8 cards.

5.2.0

• Introduced the option -logfile to append the logs into a file.
• Minor optimization on Windows for cards that are mounted on the risers.
• Improve compatibility for NiceHash.

5.1.0

• Support NiceHash.
• Fix unstable network connections in 5.0.0.
• Fix performance regressions for 1080Ti under Linux.

5.0.0

• Minor performance improvement for GTX 1060.
• Fixed performance regressions in 4.0.0 on Windows.
• Optimization on the networking layer.
• Show GPU ID in case of hardware errors.
• Introduced the option -no-timestamps which suppresses the timestamps in the logging messages.

4.0.0

• Minor performance improvement.
• Support older CPUs like Core 2 Duo.
• Support mining rigs that have more than 8 GPUs.
• Support luckpool.org.
• Removed the polling option.
• Introduced the option `-max-network-failures` which allows Bminer to exit after consecutive network failures.
• Various improvement on the UI.
• Localization for Russian and Chinese.

3.0.0

• Minor performance improvement.
• Disable CPU polling by default.
• Introduce a Web-based dashboard.
• Support slushpool.

2.1.0

• Add the -polling option to make GPU polling configurable.

Disabling polling reduces the CPU usage but it might reduce the performance in some configurations.

• Improve the stability of the network connections.
• First public release for Linux.

2.0.0

• First public release.

I certainly do not get these speeds on my GTX 1060's

• 315-325 Sol/s on GTX 1060

I get 285 around there, what am i missing.

[MagicSmoker]

@realbminer

Today there was a problem with the zenmine.pro mining pool,...don't know what was up but after investigating I've found out that bminer still has some sort of connection problems...see the picture below,...all this time the GPU was at full load,...although it didn't had a proper connection to the pool and I couldn't see it on the minning pool. Then I've switched to ewbf/dstm, both miners connected immediately and are working properly?
...
This is a huge issue! I've lost at least half of the hashrate because of this bug.

I experienced the exact same issue and reported about it a few pages back. Pretty much the worst bug imaginable for a miner, in my opinion.

[cryptoyes]

To anyone still mining on zenmine.pro, you are getting scammed (that 0% fee is fooling a lot of people) ... https://bitcointalk.org/index.php?topic=2750121

[MagicSmoker]

To anyone still mining on zenmine.pro, you are getting scammed (that 0% fee is fooling a lot of people) ... https://bitcointalk.org/index.php?topic=2750121

Interesting... I had more or less the same experience with vast underpayment with them, too, despite them finding blocks fairly consistently. I've learned to not trust any pool that doesn't charge a fee.

About 20 minutes ago I pointed a rig at http://zhash.pro/ to try them out. Although you have convinced me to mine some ZEC at Flypool - which has, indeed, proven to be very trustworthy - I still want to mainly mine ZEN. Hopefully Zcash.pro doesn't disappoint.

[shakes1118]

@realbminer

Today there was a problem with the zenmine.pro mining pool,...don't know what was up but after investigating I've found out that bminer still has some sort of connection problems...see the picture below,...all this time the GPU was at full load,...although it didn't had a proper connection to the pool and I couldn't see it on the minning pool. Then I've switched to ewbf/dstm, both miners connected immediately and are working properly?

I use following in a batch file:

Code:

-max-temperature 80 -max-network-failures 5 -gpucheck 0 -watchdog=false

...

This is a huge issue! I've lost at least half of the hashrate because of this bug.

Why are you using 'max-network-failures 5' & 'watchdog=false'? Shouldn't you leave it at the default so it will continue to try to recover the connection, especially if you are complaining of a bug saying it's not connecting?

The documentation on bminer.me states:

-max-network-failures   Default: -1   Description: Number of consecutive attempts that Bminer tries to recover from network failures. Set to -1 to keep on recovering.
-watchdog                           Default: true   Description: Automatic restart to recover from hung GPUs. Bminer exits itself in case of errors if watchdog is disabled.