how do you access the dev branch by the way ? i checked the github, but didn't saw any branch called dev except the "xmr-dev" thanks. 
Topic: [ANN] ccminer 2.3 - opensource - GPL (tpruvot) - page 103. (Read 500113 times)
I see no problem man, i'll wait, i'll continue to rely on my usual OC script, they work well how do you access the dev branch by the way ? i checked the github, but didn't saw any branch called dev except the "xmr-dev" thanks.
how do you access the dev branch by the way ? i checked the github, but didn't saw any branch called dev except the "xmr-dev" thanks. 
i dont have it built on windows for now... its why its a dev branch.. dont want to publish 100 dev versions
Ohhh i didn't knew there was a dev-branch, that explain why i was seeing ccminer 2.0 as a miner in the benchmark on yiimp. Can you share binaries ? I don't have any compiling environment on windows (and usually suck @ compiling stuff on win anyway) Thanks 
the warning is about pstate with nvml, fixed in the dev branch (2.0)
Did a few test with pool switching & failover.
Here is my config
Everything seems to work fine. Automated pool switching (with time-limit or stratum unreachable) or manual through the API work like a charm, a bit lenghty but ok, could you give me some infos about the pool settings like max-diff and scantime and if there are other useful ones ? Thanks.
On another note i tried to use the miner overclocking feature, but each time i try it, it reply that it can't query my current clock value (something to do with permissions) even though im running it as admin. Any ideas ?
Here is my config
Code:
{
"_note": "2 pool failover & switching enabled",
"pools": [{
"name": "YIIMP-LBC",
"url": "stratum+tcp://yiimp.ccminer.org:3334",
"user": "hidden",
"pass": "stats",
"max-diff": 0.0,
"scantime": 40,
"disabled": false
}, {
"name": "MINE-GPU4U-LBC",
"url": "stratum+tcp://mine.gpu4u.eu:3334",
"user": "hidden",
"pass": "stats",
"max-diff": 0.0,
"scantime": 40,
"disabled": false
}],
"algo": "lbry",
"intensity": 23.5,
"api-bind": "127.0.0.1:4444",
"api-remote": true,
"statsavg": 20,
"quiet": true,
"debug": false
}Everything seems to work fine. Automated pool switching (with time-limit or stratum unreachable) or manual through the API work like a charm, a bit lenghty but ok
, could you give me some infos about the pool settings like max-diff and scantime and if there are other useful ones ? Thanks.On another note i tried to use the miner overclocking feature, but each time i try it, it reply that it can't query my current clock value (something to do with permissions) even though im running it as admin. Any ideas ?
ah, look like they finally found the issue, yiimp ip remains between reboots :p
Huzzah \o/
ah, look like they finally found the issue, yiimp ip remains between reboots :p
its a sample "remote api" disabled by default, even with -b which is read-only stats data..
it was made to create dynamically a pool entry and switch to it... as most pools require an user, it require a special format : stratum+tcp://user:pass@host:port
this feature require the --api-remote flag
for pool switching and failover, there is sample pools.conf in the git
it was made to create dynamically a pool entry and switch to it... as most pools require an user, it require a special format : stratum+tcp://user:pass@host:port
this feature require the --api-remote flag
for pool switching and failover, there is sample pools.conf in the git
nice that could be a nice addition to my monitoring and fail over i will do some testings !
its a sample "remote api" disabled by default, even with -b which is read-only stats data..
it was made to create dynamically a pool entry and switch to it... as most pools require an user, it require a special format : stratum+tcp://user:pass@host:port
this feature require the --api-remote flag
for pool switching and failover, there is sample pools.conf in the git
it was made to create dynamically a pool entry and switch to it... as most pools require an user, it require a special format : stratum+tcp://user:pass@host:port
this feature require the --api-remote flag
for pool switching and failover, there is sample pools.conf in the git
no, the stats are just a submit of the state after 50 shares.. nothing on start and all the threads share the same code :p there is not even a related code in ccminer able to delay 4 of the 6 cards
Okay, it doesn't change a thing indeed, well config didn't changed a thing either, can't understand this issue, when i use the debug mode the thread is started and attached to all present gpu's but randomly on one or 2 of them the threads get stuck, and i also noticed that in the order of the gpus, if for example the second one in the list get stuck (gpu #1), the others ones get stuck too. like it's "waiting" for the thread to start to start the others. Again i don't understand why it does that, especially since no other one encounter this issue....
Code:
[2017-02-10 11:59:34] accepted: 86/86 (diff 5.763), 1159.99 MH/s yes!
[2017-02-10 11:59:34] accepted: 87/87 (diff 3.501), 1160.02 MH/s yes!
[2017-02-10 11:59:37] accepted: 88/88 (diff 8.780), 1159.52 MH/s yes!
[2017-02-10 11:59:37] CTRL_C_EVENT received, exiting
[2017-02-10 11:59:37] GPU #2: Intensity set to 23.5, 12582912 cuda threads
Terminate batch job (Y/N)?
As you can see also, when you interrupt the miner, the thread unlock itself.
One unrelated question, i see that you have the ability to switchpool from extended API, how does that work, how do you write a proper config file to do that ? i looked @ the example of the repo, but there isn't switching pools in it.
no, the stats are just a submit of the state after 50 shares.. nothing on start and all the threads share the same code :p there is not even a related code in ccminer able to delay 4 of the 6 cards
rmm indeed really annoying, never seen that :/ and i mine lbry on various machines..
maybe some win10 cortana intelligence :p in power saving... Cortana you are fired!
its the P8 which seems to indicate that. So maybe check the nvidia panel settings, the setting about performance "economy / optimised"
maybe some win10 cortana intelligence :p in power saving... Cortana you are fired!
its the P8 which seems to indicate that. So maybe check the nvidia panel settings, the setting about performance "economy / optimised"
Lulz,
Well the P8 state is just here because the card isn't used, it go back to P2 as soon as it is, i already disabled any power saving stuff anywhere, and it's really only this algo
Im trying to setup ccminer with a conf file instead of cmdline, and also debug mode, im also going to try if the -p stats option is hindering the process (i doubt it but i haven't tried) by the way any way to log with ccminer i didn't see anything in the help about this.
rmm indeed really annoying, never seen that :/ and i mine lbry on various machines..
maybe some win10 cortana intelligence :p in power saving... Cortana you are fired!
its the P8 which seems to indicate that. So maybe check the nvidia panel settings, the setting about performance "economy / optimised"
maybe some win10 cortana intelligence :p in power saving... Cortana you are fired!
its the P8 which seems to indicate that. So maybe check the nvidia panel settings, the setting about performance "economy / optimised"
first, ensure they are really inactive, did you check afterburner graphes (or nvidia-smi output)
Yes, i checked current gpu usage through nvidia-smi, and afterburner, and also nvidia-inspector, they're not running @ all, my wall power draw is also much lower than usual. Im gonna do a recheck/restest right now and try to post you useful infos.
Code:
[2017-02-10 11:05:11] Adding 4194304 threads to intensity 23, 12582912 cuda threads
[2017-02-10 11:05:11] Starting on stratum+tcp://mine.gpu4u.eu:3334
[2017-02-10 11:05:11] 6 miner threads started, using 'lbry' algorithm.
[2017-02-10 11:05:11] Stratum difficulty set to 32 (0.12500)
[2017-02-10 11:05:13] GPU #0: Intensity set to 23.5, 12582912 cuda threads
[2017-02-10 11:05:13] GPU #5: Intensity set to 23.5, 12582912 cuda threads
[2017-02-10 11:05:13] GPU #1: Intensity set to 23.5, 12582912 cuda threads
[2017-02-10 11:05:13] accepted: 1/1 (diff 1.402), 269.93 MH/s yes!
[2017-02-10 11:05:14] accepted: 2/2 (diff 0.347), 282.67 MH/s yes!
[2017-02-10 11:05:14] accepted: 3/3 (diff 0.163), 281.32 MH/s yes!
[2017-02-10 11:05:15] accepted: 4/4 (diff 0.212), 279.62 MH/s yes!
[2017-02-10 11:05:17] accepted: 5/5 (diff 0.640), 279.68 MH/s yes!
[2017-02-10 11:05:23] accepted: 6/6 (diff 0.749), 279.34 MH/s yes!
[2017-02-10 11:05:24] accepted: 7/7 (diff 4.338), 268.71 MH/s yes!
[2017-02-10 11:05:26] GPU #2: Intensity set to 23.5, 12582912 cuda threads
[2017-02-10 11:05:29] accepted: 8/8 (diff 0.369), 271.18 MH/s yes!
[2017-02-10 11:05:31] accepted: 9/9 (diff 0.202), 272.92 MH/s yes!
[2017-02-10 11:05:32] accepted: 10/10 (diff 0.170), 273.38 MH/s yes!
[2017-02-10 11:05:32] accepted: 11/11 (diff 0.152), 273.25 MH/s yes!
[2017-02-10 11:05:34] accepted: 12/12 (diff 0.223), 273.34 MH/s yes!
[2017-02-10 11:05:36] accepted: 13/13 (diff 0.416), 274.32 MH/s yes!
[2017-02-10 11:05:38] accepted: 14/14 (diff 0.370), 274.65 MH/s yes!
Code:
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 378.49 Driver Version: 378.49 |
|-------------------------------+----------------------+----------------------+
| GPU Name TCC/WDDM | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 1070 WDDM | 0000:01:00.0 Off | N/A |
| 30% 63C P2 112W / 111W | 217MiB / 8192MiB | 99% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 1070 WDDM | 0000:02:00.0 Off | N/A |
| 18% 48C P8 8W / 111W | 165MiB / 8192MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 1070 WDDM | 0000:03:00.0 Off | N/A |
| 20% 48C P8 8W / 111W | 165MiB / 8192MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce GTX 1070 WDDM | 0000:04:00.0 Off | N/A |
| 22% 50C P2 28W / 111W | 155MiB / 8192MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 4 GeForce GTX 1070 WDDM | 0000:05:00.0 Off | N/A |
| 23% 50C P2 28W / 111W | 155MiB / 8192MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 5 GeForce GTX 1070 WDDM | 0000:06:00.0 Off | N/A |
| 22% 50C P8 8W / 111W | 165MiB / 8192MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 1016 C+G C:\Windows\System32\dwm.exe N/A |
| 0 3544 C+G C:\Windows\explorer.exe N/A |
| 0 4392 C+G ...ost_cw5n1h2txyewy\ShellExperienceHost.exe N/A |
| 0 4588 C+G ...eamViewer\Version9\TeamViewer_Desktop.exe N/A |
| 0 4632 C+G ...indows.Cortana_cw5n1h2txyewy\SearchUI.exe N/A |
| 0 6028 C ...r-rel1.8.4-x64-tpruvot\ccminer-80-x64.exe N/A |
| 1 6028 C ...r-rel1.8.4-x64-tpruvot\ccminer-80-x64.exe N/A |
| 2 6028 C ...r-rel1.8.4-x64-tpruvot\ccminer-80-x64.exe N/A |
| 3 6028 C ...r-rel1.8.4-x64-tpruvot\ccminer-80-x64.exe N/A |
| 4 6028 C ...r-rel1.8.4-x64-tpruvot\ccminer-80-x64.exe N/A |
| 5 6028 C ...r-rel1.8.4-x64-tpruvot\ccminer-80-x64.exe N/A |
+-----------------------------------------------------------------------------+
After a bit (a few minutes), it will go up opening those 4 threads that started earlier.
Code:
[2017-02-10 11:07:57] accepted: 130/175 (diff 0.828), 1148.06 MH/s yes!
[2017-02-10 11:07:59] accepted: 131/176 (diff 1.636), 1148.00 MH/s yes!
[2017-02-10 11:07:59] accepted: 132/177 (diff 0.984), 1148.56 MH/s yes!
[2017-02-10 11:07:59] accepted: 133/178 (diff 0.984), 1148.56 MH/s yes!
[2017-02-10 11:07:59] accepted: 134/179 (diff 1.264), 1148.21 MH/s yes!
[2017-02-10 11:08:00] accepted: 135/180 (diff 0.513), 1148.20 MH/s yes!
[2017-02-10 11:08:00] accepted: 136/181 (diff 1.421), 1148.22 MH/s yes!
[2017-02-10 11:08:05] accepted: 137/182 (diff 2.486), 1147.59 MH/s yes!
[2017-02-10 11:08:05] accepted: 138/183 (diff 2.486), 1147.59 MH/s yes!
[2017-02-10 11:08:07] accepted: 139/184 (diff 2.158), 1147.62 MH/s yes!
[2017-02-10 11:08:09] accepted: 140/185 (diff 0.630), 1147.22 MH/s yes!
Code:
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 378.49 Driver Version: 378.49 |
|-------------------------------+----------------------+----------------------+
| GPU Name TCC/WDDM | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 1070 WDDM | 0000:01:00.0 Off | N/A |
| 32% 64C P2 106W / 111W | 217MiB / 8192MiB | 97% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 1070 WDDM | 0000:02:00.0 Off | N/A |
| 30% 64C P2 89W / 111W | 165MiB / 8192MiB | 99% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 1070 WDDM | 0000:03:00.0 Off | N/A |
| 35% 66C P2 112W / 111W | 165MiB / 8192MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce GTX 1070 WDDM | 0000:04:00.0 Off | N/A |
| 5% 49C P2 28W / 111W | 155MiB / 8192MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 4 GeForce GTX 1070 WDDM | 0000:05:00.0 Off | N/A |
| 0% 43C P8 8W / 111W | 165MiB / 8192MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 5 GeForce GTX 1070 WDDM | 0000:06:00.0 Off | N/A |
| 31% 64C P2 111W / 111W | 165MiB / 8192MiB | 99% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 1016 C+G C:\Windows\System32\dwm.exe N/A |
| 0 3544 C+G C:\Windows\explorer.exe N/A |
| 0 4392 C+G ...ost_cw5n1h2txyewy\ShellExperienceHost.exe N/A |
| 0 4588 C+G ...eamViewer\Version9\TeamViewer_Desktop.exe N/A |
| 0 4632 C+G ...indows.Cortana_cw5n1h2txyewy\SearchUI.exe N/A |
| 0 6028 C ...r-rel1.8.4-x64-tpruvot\ccminer-80-x64.exe N/A |
| 1 6028 C ...r-rel1.8.4-x64-tpruvot\ccminer-80-x64.exe N/A |
| 2 6028 C ...r-rel1.8.4-x64-tpruvot\ccminer-80-x64.exe N/A |
| 3 6028 C ...r-rel1.8.4-x64-tpruvot\ccminer-80-x64.exe N/A |
| 4 6028 C ...r-rel1.8.4-x64-tpruvot\ccminer-80-x64.exe N/A |
| 5 6028 C ...r-rel1.8.4-x64-tpruvot\ccminer-80-x64.exe N/A |
+-----------------------------------------------------------------------------+
And after this sometimes it will start the thread of the 2 missing cards, but sometimes it doesn't
Code:
[2017-02-10 11:09:06] accepted: 162/207 (diff 7.438), 1146.97 MH/s yes!
[2017-02-10 11:09:16] accepted: 163/208 (diff 2.432), 1146.98 MH/s yes!
[2017-02-10 11:09:19] Stratum difficulty set to 512 (2.00000)
[2017-02-10 11:09:32] accepted: 164/209 (diff 2.298), 1147.95 MH/s yes!
[2017-02-10 11:09:37] accepted: 165/210 (diff 3.336), 1147.97 MH/s yes!
[2017-02-10 11:09:40] accepted: 166/211 (diff 2.963), 1147.76 MH/s yes!
[2017-02-10 11:10:01] accepted: 167/212 (diff 14.531), 1147.76 MH/s yes!
[2017-02-10 11:10:07] accepted: 168/213 (diff 4.229), 1147.75 MH/s yes!
[2017-02-10 11:10:08] accepted: 169/214 (diff 2.068), 1147.62 MH/s yes!
[2017-02-10 11:10:15] GPU #3: Intensity set to 23.5, 12582912 cuda threads
[2017-02-10 11:10:21] accepted: 170/215 (diff 9.569), 1738.08 MH/s yes!
[2017-02-10 11:10:22] accepted: 171/216 (diff 4.519), 1738.04 MH/s yes!
[2017-02-10 11:10:23] accepted: 172/217 (diff 2.933), 1738.25 MH/s yes!
[2017-02-10 11:10:25] accepted: 173/218 (diff 5.600), 1737.90 MH/s yes!
[2017-02-10 11:10:33] accepted: 174/219 (diff 20.750), 1738.99 MH/s yes
Code:
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 378.49 Driver Version: 378.49 |
|-------------------------------+----------------------+----------------------+
| GPU Name TCC/WDDM | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 1070 WDDM | 0000:01:00.0 Off | N/A |
| 34% 64C P2 111W / 111W | 217MiB / 8192MiB | 99% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 1070 WDDM | 0000:02:00.0 Off | N/A |
| 32% 63C P2 107W / 111W | 165MiB / 8192MiB | 98% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 1070 WDDM | 0000:03:00.0 Off | N/A |
| 37% 65C P2 108W / 111W | 165MiB / 8192MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce GTX 1070 WDDM | 0000:04:00.0 Off | N/A |
| 34% 65C P2 98W / 111W | 165MiB / 8192MiB | 99% Default |
+-------------------------------+----------------------+----------------------+
| 4 GeForce GTX 1070 WDDM | 0000:05:00.0 Off | N/A |
| 28% 63C P2 111W / 111W | 165MiB / 8192MiB | 99% Default |
+-------------------------------+----------------------+----------------------+
| 5 GeForce GTX 1070 WDDM | 0000:06:00.0 Off | N/A |
| 33% 64C P2 113W / 111W | 165MiB / 8192MiB | 98% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 1016 C+G C:\Windows\System32\dwm.exe N/A |
| 0 3544 C+G C:\Windows\explorer.exe N/A |
| 0 4392 C+G ...ost_cw5n1h2txyewy\ShellExperienceHost.exe N/A |
| 0 4588 C+G ...eamViewer\Version9\TeamViewer_Desktop.exe N/A |
| 0 4632 C+G ...indows.Cortana_cw5n1h2txyewy\SearchUI.exe N/A |
| 0 6028 C ...r-rel1.8.4-x64-tpruvot\ccminer-80-x64.exe N/A |
| 1 6028 C ...r-rel1.8.4-x64-tpruvot\ccminer-80-x64.exe N/A |
| 2 6028 C ...r-rel1.8.4-x64-tpruvot\ccminer-80-x64.exe N/A |
| 3 6028 C ...r-rel1.8.4-x64-tpruvot\ccminer-80-x64.exe N/A |
| 4 6028 C ...r-rel1.8.4-x64-tpruvot\ccminer-80-x64.exe N/A |
| 5 6028 C ...r-rel1.8.4-x64-tpruvot\ccminer-80-x64.exe N/A |
+-----------------------------------------------------------------------------+
As you see it take up to 5-8mn to get to full speed, but sometimes it doesn't even after 30mn of mining, also i checked it affect any cards, not always the same. I have this behavior on all my 10 rigs, i run the miner in admin, i tried on 2 rigs, 8 different drivers version. I dunno what to do
, my monitoring script has sometimes to reboot the rig twice or restart the miner a couple of time before i get full speed in a timely manner.I also checked if that wasn't an issue with either remaining stuff in memory & such by doing reboot, and also i tried it without using any remote app like teamviewer or vnc, but the behavior is the same, and i use ccminer to mine lbry, dcr, ftc, vtc this is the only algo that does this. I also checked pool & ccminer api numbers and it match what i see.
And when it take 5-8mn to reach full speed, it's not really full speed i have about 1% less hash than when it reach full speed @ the start of the miner. It's really weird
first, ensure they are really inactive, did you check afterburner graphes (or nvidia-smi output)
Hmm, dunno, never experienced that (your lbry issue)
Else for this url, i just setup an automated task to ensure a DNS update without delay... (for mine.gpu4u.eu only first). I hope the techs will stop to play to reset the router, that start to bug me a lot...
Else for this url, i just setup an automated task to ensure a DNS update without delay... (for mine.gpu4u.eu only first). I hope the techs will stop to play to reset the router, that start to bug me a lot...
I see, damn i can't understand it, and i have it across all my rigs, i tried 8 different drivers version always the same, it there anything i could do to give you any useful debug information so that you could look into it ?
Hmm, dunno, never experienced that (your lbry issue)
Else for this url, i just setup an automated task to ensure a DNS update without delay... (for mine.gpu4u.eu only first). I hope the techs will stop to play to reset the router, that start to bug me a lot...
Else for this url, i just setup an automated task to ensure a DNS update without delay... (for mine.gpu4u.eu only first). I hope the techs will stop to play to reset the router, that start to bug me a lot...
yes, i experienced that too on windows... temporary, unable to explain... Lucky me i woke up exactly at the cut time :p
try to ping it after an ipconfig /flushdns, i think the ip is wrong in your cache. In theory this case is auto resolved in a few minutes automatically
try to ping it after an ipconfig /flushdns, i think the ip is wrong in your cache. In theory this case is auto resolved in a few minutes automatically
I had added already the flushdns in my monitoring script, hence why it seemed weird it wasn't working especially since the website was, maybe there is some other factors.
Still experiencing issue with lbry and the miner, pretty annoying those cards that doesn't start or start 4-8mn after the others, i tried pretty much everything but only this algo give me this much headaches
yes, i experienced that too on windows... temporary, unable to explain... Lucky me i woke up exactly at the cut time :p
try to ping it after an ipconfig /flushdns, i think the ip is wrong in your cache. In theory this case is auto resolved in a few minutes automatically
try to ping it after an ipconfig /flushdns, i think the ip is wrong in your cache. In theory this case is auto resolved in a few minutes automatically
both address work for the website (yiimp & minegpu) but only the yiimp adress work for pool, the minegpu doesn't work anymore (issue begun @8:18 am)
Code:
[2017-02-10 08:18:29] Stratum connection failed: Failed to connect to mine.gpu4u.eu port 3334: Timed out
[2017-02-10 08:18:29] ...retry after 30 seconds
Jump to: