Topic: EWBF's Cuda Equihash Miner 0.6 - page 16. (Read 85776 times)

Your command line will get a little bit longer than it was before you put "--fee 0" in it.

what does if i put in the command line --fee 0 ¿?

EWBF Cuda Equihash Miner v0.5

Greetings!
This is the initial release of a new miner for Equihash algorithm.
It is based on my last Zcash miner and almost completely repeats it.
Now closer to the topic:
*  Parameter "solver" is disabled.
*  Solver for equihash 200,9 has been deleted.
*  Solvers for Equihash 192,7, 144,5, 96,5 and 210,9 has been added
*  Added timestamps in the output to the screen and to the log file.
*  Argument --algo is added, allow you to select Equihash variant allowed values 144_5, 192_7, 96_5, 210_9, zhash, aion. This parameter is mandatory.
*  Argument --pers is added, allow you to set personalization string (8 charachters) for equihash algorithm. This parameter is optional. Equihash by default uses the string "ZcashPoW", many other coins also use this string, but not all, some coins use their own string, and these are all differences, so for some coins, you need to set the --pers option to the required string, for example, Zero coin: https://bitcointalksearch.org/topic/annzerzero-your-transactions-are-your-business-3310714  uses the string "ZERO_PoW" and for mining this coin you need to pass arguments --algo 192_7 --pers ZERO_PoW ....
Fee is presented and by default 2%, argument --fee is presented too.

v0.5
* 96_5 fixed the problem with cropped performance on fast (1080ti, Titan) gpu.
* 144_5 Speed up by 3-15% depends on the hardware.
* 210_9 Speed up by 2%.
* 210_9 Fixed "low difficulty shares" problem, on Aion pools.
* 210_9 can now be used via --algo 210_9, I recommend using --algo aion for Aion mining, this will help you avoid problems with the wrong personalization string.
* Added option --intensity, this option will not increase performance, only slightly reduce the gpu usage, if you set it to 1. Works like --cuda_devices argument,
   for example: --intensity 64 64 1 64 64 will apply the intensity 1 to the device with id 2.
 Special features (These features are added for specific projects,do not use these parameters on conventional pools):
* Added option --pers auto, Allow the pool to manage the personalization string. (Profit switching). (http://zergpool.com)
* Added option --algo 144_5_EXCC_D For ExchangeCoin.

v0.4
*  Added new solver for Equihash 210,9. Available only with --algo aion (this solver is in beta status)
*  Failover pools can now be specified via command-line arguments, just repeat the credentials set, but do not shuffle them (see Example below)
*  Improved performance for algo 144_5 and maxwell gpus
*  Fixed launching of devices

Known issues (mostly will be fixed)
*  Equihash 96_5 Can be slower in cuda 8 versions.
*  Performance counters may display an incorrect speed during reconnection.

Expected performance:

96_5 uses ~1.6GB vram
 1050ti   ~7.5 KS/s  
 1060    ~13.5 KS/s
 1070    ~19.5 KS/s
 1080    ~23.5 KS/s
 1080ti    ~34.5 KS/s

192_7 uses ~2.5GB vram
 1050ti    ~8 S/s
 1060    ~13 S/s
 1070    ~19 S/s
 1080    ~22 S/s
 1080ti    ~30 S/s

144_5 uses ~2.0GB vram
 1050ti   ~15 S/s  
 1060    ~27 S/s
 1070    ~40 S/s
 1080    ~45 S/s
 1080ti    ~64 S/s

210_9(aion) uses 1.2G vram
 1050ti   ~75 S/s
 1060    ~130 S/s
 1070    ~190 S/s
 1080    ~210 S/s
 1080ti  ~320 S/s

Please note, that this is initial release, and it can be baggy or incompatible with many coins or pools.
Miner compiled with cuda 9.1 and cuda 8.0 for x64 linux and windows. Support devices with compute capability 5.0 and higher.

Windiws    https://mega.nz/#F!fsAlmZQS!CwVgFfBDduQI-CbwVkUEpQ
Linux        https://mega.nz/#F!3xYlSJDK!kG4kVLg1arbBuq1dd8u9aA

Linux        https://drive.google.com/open?id=1jUhXYysli_x6MH_wQ9lY07c68Ze7WM8g
Windiws   https://drive.google.com/open?id=1anfDRDVc_Fs_NceuZNuDK8HWZgcCdM3A

Usage examples (batch files):
Basic Example:
Failover pools up to 8 pools:

hello, guys. yeah, i have 2 1060 gpus on windows 10. in verison 0.3 it works fine, but 0.4, 0.5 im take crushing error who caused reboot my farm with cool message - thread exited with message the launch timed out and was terminated.
WAIDW?

Yes, except --solver option.


It is difficult, but possible.


This miner does not support equihash 200,9. I also think a couple of months, and it will be unprofitable for the GPU because of the asic's.


This is actually a common problem, you need to make sure that your overclocking is stable, note that different algorithms load gpu in different ways. Thus, stable overclocking on one algorithm does not guarantee stability for others.


With fewer GPUs, no problems?

hello, guys. yeah, i have 2 1060 gpus on windows 10. in verison 0.3 it works fine, but 0.4, 0.5 im take crushing error who caused reboot my farm with cool message - thread exited with message the launch timed out and was terminated.
WAIDW?

this old readmy (previous version for zec) is fully work with this new ewbf miner? https://github.com/nemosminer/EWBF-Zec-Miner/blob/master/Help.txt

Any possible improvements for 96_5, or this is the limit?

dear i know maybe its stupid question but whats the alg for Zcash and whats the miner command line will be . thanks and sorry again

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

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

  ok what to do. will wait so. but  i like EWBF

fukanoshi call his miner as a fastest one, anyone checked already ewbf VS fukanoshi?

thanks for your help but may i know what algo shall i use in EWBF i mean like 210_9 or something , because the new one i must put the alg number on it right
thanks again for your help

*  Solver for equihash 200,9 has been deleted.

Zcash uses Equihash-algo. Try ZecMiner64 or EWBF miner:
miner --server us-east.equihash-hub.miningpoolhub.com --user username.workername --pass x --port 20570

dear i know maybe its stupid question but whats the alg for Zcash and whats the miner command line will be . thanks and sorry again

I am having issues with the API loading. It states the API failed every so often.