EWBF's Cuda Equihash Miner 0.6

[EWBF_]

Good news everyone! v0.5 delivered.

Up to 40 sol/s with GTX 1070 (no overclock, 70% power) vs 33 sol/s on v0.3.
EWBF, any chance you can publish checksums for your distros? just for paranoid people like myself....

OK, no problem.

[Eeroz]

Dumb question on my part likely - but how did you get Power usage stats to display there in your log output?  I never have seen that, and could DEFINITELY use that to my advantage.  Thanks for sharing, great stats thanks to v0.5...nice indeed!  Cheers.

If using the cfg file, change "pec" from 0 to 1
If using command line options, use --pec 1

[Trololino]

Good news everyone! v0.5 delivered.

Well the hashrate miner is showing has increased, rigs are more stable. But for some reason, I mine less , and the difficulty hasnt increased that much. Dont know if its the pool not reacting well to new miner, or there is something wrong with miner. It should be same or more 

[bragmining]

Can we get some more documentation on how this new functionality worksL

* Added option --pers auto, Allow the pool to manage the personalization string. (Profit switching). (/http://zergpool.com)

[EWBF_]

Can we get some more documentation on how this new functionality worksL

* Added option --pers auto, Allow the pool to manage the personalization string. (Profit switching). (/http://zergpool.com)

It's very simple, the pool should send a modified mining_notify method (the differences are in bold): {"id": null, "method": "mining.notify", "params": ["JOB_ID", "VERSION", "PREVHASH", "MERKLEROOT", "RESERVED", "TIME", "BITS", CLEAN_JOBS, "144_5", "BgoldPoW"]}
And the miner will use the specified personalization (the 9th element of the params array). that's all.
The 8th element, currently not used, you must set the algorithm in it.

[winklebingkle]

Im having issues with setting the -fee 0 in the miner.cfg. I am still seeing the miner targetting to what im assuming is the miner dev fee. Let me know if this is intended and that you have removed the -fee 0 option. I am mining the aion algorith btw.

[bragmining]

Im having issues with setting the -fee 0 in the miner.cfg. I am still seeing the miner targetting to what im assuming is the miner dev fee. Let me know if this is intended and that you have removed the -fee 0 option. I am mining the aion algorith btw.

Are there any side effects to setting dev fee to 0?  Does it cause miner to mine slower?

[crypper]

Im having issues with setting the -fee 0 in the miner.cfg. I am still seeing the miner targetting to what im assuming is the miner dev fee. Let me know if this is intended and that you have removed the -fee 0 option. I am mining the aion algorith btw.

Are there any side effects to setting dev fee to 0?

Yes: GREED is one of seven deadly sins! You could set the fee to at least 0.1% to support the dev. Especially considering 20% boost in hashrate with the most recent v0.5.

[kantoi]

Good news everyone! v0.5 delivered.

Sweet I just tried the new version and it looks really good so far for my 1070 and 96.5 algo. I get around 600 Sol/s more compared to the v0.4 - nice thank you very much.

[mySmile28]

Im having issues with setting the -fee 0 in the miner.cfg. I am still seeing the miner targetting to what im assuming is the miner dev fee. Let me know if this is intended and that you have removed the -fee 0 option. I am mining the aion algorith btw.

Are there any side effects to setting dev fee to 0?  Does it cause miner to mine slower?

checked on two identical rigs, did not see any difference either in hashrate or in shares

[crypper]

Good news everyone! v0.5 delivered.

Sweet I just tried the new version and it looks really good so far for my 1070 and 96.5 algo. I get around 600 Sol/s more compared to the v0.4 - nice thank you very much.

Has anyone tried alternative miners? What kind of hash rates do they offer compared with EWBF.
I mean considering that most people use EWBF for modern equihash algos (and those who don't use will switch soon if they find out that it offers better hashrate), then there is not much benefit for miners from increased hashrate in new v0.5. The net hash will increase, the income won't change.
Is that how it works?

[swisstrader]

Tested results after 24 hours:

ZHash 144_5 uses ~2.0GB VRAM

1070        ~41 to 46 Sol/s     //tuned PL=140W, OC=50/1000

1080 Ti    ~64 to 71 Sol/s     //tuned PL=220W, OC=100/1000      test rig with 4 x 1080 Ti + 6 x 1070 = min. 517 to max. 535 Sol/s; Avg. = 526 Sol/s
                                                                                                                                                              Efficiency Avg. = 0.31 Sol/Ws = 0.31 Sol/J

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

1070 Ti    ~43 to 50 Sol/s     //tuned PL=120W, OC=200/1200      test rig with 5 x 1070 Ti                  = min. 227 to max. 238 Sol/s; Avg. = 233 Sol/s
                                                                                                                                                              Efficiency Avg. = 0.40 Sol/Ws = 0.40 Sol/J

[swisstrader]

Comparison of my 5 x 1070 Ti rig with new published miniZ miner:



Cards are too hot (68 °C) and hash rate result only 190 sol/s,
with EWBF v0.5 hash rate = 233 sol/s at max. 64 °C (room temp. 28 °C).

[crypper]

Tested results after 24 hours:

ZHash 144_5 uses ~2.0GB VRAM

1070        ~41 to 46 Sol/s     //tuned PL=140W, OC=50/1000

Which 1070 can handle mc +1000?

[bragmining]

Is anyone else experiencing an increase in hashrate and a drop in shares while using v0.5 on BTG?

[meinerneiner]

UPDATE: 1080ti - just received this card, getting 70-71 sol/s of 144,5 with slight overclock 97/282 and 95% PL.  FUN FUN FUN!

[Scrubzer0]

Loving the higher hashrate

BUT STILL HAVING PROBLEMS WITH 12 CARD RIGS, it runs fine for about 5 minutes then crashes, GPU dump errors, help please, using SMOS

[alexivan_58]

Sometimes miner crashes and tries to restart:

"
14:06:42 CUDA: Device: 6 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:43 WARNING: Looks like GPU7 are stopped. Restarting...
14:06:43 INFO: GPU7 are restarted.
14:06:43 CUDA: Device: 7 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:44 WARNING: Looks like GPU0 are stopped. Restarting...
14:06:44 INFO: GPU0 are restarted.
14:06:44 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:44 WARNING: Looks like GPU1 are stopped. Restarting...
14:06:44 INFO: GPU1 are restarted.
14:06:44 CUDA: Device: 1 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:44 WARNING: Looks like GPU2 are stopped. Restarting...
14:06:44 INFO: GPU2 are restarted.
14:06:44 CUDA: Device: 2 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:44 WARNING: Looks like GPU3 are stopped. Restarting...
14:06:44 INFO: GPU3 are restarted.
14:06:44 CUDA: Device: 3 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
14:06:45 WARNING: Looks like GPU4 are stopped. Restarting...
14:06:45 INFO: GPU4 are restarted.
14:06:45 CUDA: Device: 4 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
"


I kill task  manually and start the task again, then everything works fine

It would be very good if he himself began anew independently

windows 10, 8 cards : 6/1070 +2/1080ti
drivers nvidia 01.06.2018  ver. 24.21.13.9811

[Globalminingcorp]

Great work EWBF, i have two 1050ti card running and they are on average 7% faster than version 0.4.

[gs777]

Thanks man!
My gtx1080 and 1070 rigs hashing 15% more with v0.5
your EWBF v5.0 miner is the best z_hush miner!