Topic: DiabloMiner GPU Miner - page 38. (Read 866596 times)
Update: Improved error handling for argument parsing, will now quit if you do not supply enough connection parameters, or try to use 0 with -D
Windows Defender FAIL, it is telling me diablominer may be a virus and ask me to delete it. Danger level: average
Of course it's a false positive, diablominer is safe, but for MICROSOFT, it isn't.
Program:Win32/BitCoinMiner
Program:MacOS/BitCoinMiner
Program:Linux/BitCoinMiner
Program:Solaris/BitCoinMiner
So much fail.
Also it shows that microsoft consider miners as dangerous software
Of course it's a false positive, diablominer is safe, but for MICROSOFT, it isn't.
Program:Win32/BitCoinMiner
Program:MacOS/BitCoinMiner
Program:Linux/BitCoinMiner
Program:Solaris/BitCoinMiner
So much fail.
Also it shows that microsoft consider miners as dangerous software
There has been an actual virus that distributes miners as their payloads, and the authors of the anti-viruses are too stupid to tag the right binaries (ie, the virus instead of the otherwise legitimate payload). The same has happened to cgminer, btw.
Windows Defender FAIL, it is telling me diablominer may be a virus and ask me to delete it. Danger level: average
Of course it's a false positive, diablominer is safe, but for MICROSOFT, it isn't.
Program:Win32/BitCoinMiner
Program:MacOS/BitCoinMiner
Program:Linux/BitCoinMiner
Program:Solaris/BitCoinMiner
So much fail.
Also it shows that microsoft consider miners as dangerous software
Of course it's a false positive, diablominer is safe, but for MICROSOFT, it isn't.
Program:Win32/BitCoinMiner
Program:MacOS/BitCoinMiner
Program:Linux/BitCoinMiner
Program:Solaris/BitCoinMiner
So much fail.
Also it shows that microsoft consider miners as dangerous software
Update: Bug in multipool pool advance fixed, uncovered by return to primary. D'oh.
Update: Added two often requested features: return to primary pool every 100 minutes when using multipool, and added a feature to automatically donate, use -b.
Update: Moved two adds to host code from kernel, made it faster.
DiabloD3, what are those settings -w 64 -v 36 compared to cgminer options? I tried -v 4 -w 64.. much slower.
What hardware, driver, and SDK? I tested this on 11.12 and SDK 2.6, normal options apply to everyone else.
windows x64, 3 x raden hd 6990, drivers 11.12 with I think SDK 2.6
Much slower than -v 2 -w 256 on that same combination?
-v 4 -w 64 is about 50mh slower each GPU, the same with -v 2 -w 256. I just wanted to know the settings with cgminer compared to your miner using -v 36. What is -v 36 anyway?
P.S. the best result is with -v 2 -w 128 so far
-v 4 on cgminer seems to be the same thing as -v 36 on mine.
DiabloD3, what are those settings -w 64 -v 36 compared to cgminer options? I tried -v 4 -w 64.. much slower.
What hardware, driver, and SDK? I tested this on 11.12 and SDK 2.6, normal options apply to everyone else.
windows x64, 3 x raden hd 6990, drivers 11.12 with I think SDK 2.6
Much slower than -v 2 -w 256 on that same combination?
-v 4 -w 64 is about 50mh slower each GPU, the same with -v 2 -w 256. I just wanted to know the settings with cgminer compared to your miner using -v 36. What is -v 36 anyway?
P.S. the best result is with -v 2 -w 128 so far
DiabloD3, what are those settings -w 64 -v 36 compared to cgminer options? I tried -v 4 -w 64.. much slower.
What hardware, driver, and SDK? I tested this on 11.12 and SDK 2.6, normal options apply to everyone else.
windows x64, 3 x raden hd 6990, drivers 11.12 with I think SDK 2.6
Much slower than -v 2 -w 256 on that same combination?
DiabloD3, what are those settings -w 64 -v 36 compared to cgminer options? I tried -v 4 -w 64.. much slower.
What hardware, driver, and SDK? I tested this on 11.12 and SDK 2.6, normal options apply to everyone else.
windows x64, 3 x raden hd 6990, drivers 11.12 with I think SDK 2.6
DiabloD3, what are those settings -w 64 -v 36 compared to cgminer options? I tried -v 4 -w 64.. much slower.
What hardware, driver, and SDK? I tested this on 11.12 and SDK 2.6, normal options apply to everyone else.
DiabloD3, what are those settings -w 64 -v 36 compared to cgminer options? I tried -v 4 -w 64.. much slower.
Did some performance testing:
Catalyst 11.12 on Radeon 5850 at 960/320
-v 2 -w 256 -f 1
SDK 2.1: 400
SDK 2.4: 387
SDK 2.5: 387
SDK 2.6: 358
-v 2 -w 256 -f 1 -a
SDK 2.1: 400
SDK 2.4: 387
SDK 2.5: 387
SDK 2.6: 357
So. SDK 2.6 performance is pretty low and also phatk-like arrays no longer work against the driver with the most optimum settings. Lets try everything else.
-w 256
-v 1: 306
-v 2: 357
-v 3: 325
-v 4: 341
-v 5: 225
-v 6: 212
-v 18: 318
-v 19: 301
-v 20: 211
-v 21: 210
-v 36: 238
-v 40: 214
-w 64
-v 1: 306
-v 2: 349
-v 3: 340
-v 4: 348
-v 5: 303
-v 6: 257
-v 18: 313
-v 19: 305
-v 20: 297
-v 21: 297
-v 36: 365
-v 40: 214
-w 128
-v 2: 355
-v 4: 344
-v 36: 326
-w 192
-v 2: 351
-v 4: 297
-v 36: 323
With or without -a, the best seems to be -w 64 -v 36 for SDK 2.6. Weird. Still a fair bit slower than 2.1 and 2.4/2.5 though.
Catalyst 11.12 on Radeon 5850 at 960/320
-v 2 -w 256 -f 1
SDK 2.1: 400
SDK 2.4: 387
SDK 2.5: 387
SDK 2.6: 358
-v 2 -w 256 -f 1 -a
SDK 2.1: 400
SDK 2.4: 387
SDK 2.5: 387
SDK 2.6: 357
So. SDK 2.6 performance is pretty low and also phatk-like arrays no longer work against the driver with the most optimum settings. Lets try everything else.
-w 256
-v 1: 306
-v 2: 357
-v 3: 325
-v 4: 341
-v 5: 225
-v 6: 212
-v 18: 318
-v 19: 301
-v 20: 211
-v 21: 210
-v 36: 238
-v 40: 214
-w 64
-v 1: 306
-v 2: 349
-v 3: 340
-v 4: 348
-v 5: 303
-v 6: 257
-v 18: 313
-v 19: 305
-v 20: 297
-v 21: 297
-v 36: 365
-v 40: 214
-w 128
-v 2: 355
-v 4: 344
-v 36: 326
-w 192
-v 2: 351
-v 4: 297
-v 36: 323
With or without -a, the best seems to be -w 64 -v 36 for SDK 2.6. Weird. Still a fair bit slower than 2.1 and 2.4/2.5 though.
Updated: Added a whitelist to only BFI_INT patch on GPUs we know it works, should fix 79xx GCN until a better solution is discovered.
Some of the 7xxx family apparently are going to be VLIW4, but I don't know the code names for these for sure yet, I'll have to add those later.
Some of the 7xxx family apparently are going to be VLIW4, but I don't know the code names for these for sure yet, I'll have to add those later.
Interested in 79xx support? See https://bitcointalksearch.org/topic/want-legit-7970-testingbenchmarking-and-tuning-for-cgminer-and-diablominer-55540
Update: Moved execution threads back down to 2 now that AMD has fixed the CPU usage issue, and merged patch to make DM work better on chains that have difficulty below 1
Silly question, when I try to open the miner, it instacloses. Any ideas?
Its not a GUI app, use the command line.
Silly question, when I try to open the miner, it instacloses. Any ideas?
is it possible to make this mine at about 3/4 of full speed on windows? it seems like the -f doesnt do anything when i set it to more than a few hundred.
No. If you need GPU performance, just shut the miner off when you need it.
is it possible to make this mine at about 3/4 of full speed on windows? it seems like the -f doesnt do anything when i set it to more than a few hundred.
Jump to: