I ran the 2.2 version of TPruvot ccminer w/ skunk and got horrible hashrates. I will recompile and test it again, but for now, krnlx is the fastest for me. I'm not sure why there is a perceived drop of 30% in his setup, but I'm not seeing that at all. I'm mining exactly at the expected coin rate per day based on both whattomine.com and crypto-economy.com calculators (450mh/s nets me around 550 coins a day +/- 25). I will note that when I tried changing clock settings a little higher it really affected hashrates, dropping them over time considerably. There is definitely a 'sweet spot' clock rate for skunk, and deviation appears to create greatly reduced production. Also mining at -i 26 seems to have reduced my hashrates, so -i 25 is the proper setting for 1070 / 1080 Ti at least. Lower settings or leaving -i blank greatly reduce hashrates, as is to be expected.
I'll update with the results of a recompile with tpruvot's most recent ccminer release on 0018.
Thanks for keeping an eye on this.
EDIT: the latest tpruvot ccminer release runs at just about the same hashrate as krnlx within 1-2mh/s (463mh/s vs. 462mh/s) and in a 2 hour test it mined 26-27 coins an hour on sigt.pool.mn which is a small number more than I was mining before, but it's a shjort test length so I'll update again after 24 hours to get a better average. I was able to run tpruvot with skunk from command line in guake, but it crashes for some reason when running from the script almost immediately after it starts mining (before watchdog kicks in). Not sure why that's happening, the command line is the same in both as I have it configured.
In the end, I don't see a dramatic difference between the two miners' performance except that I know krnlx runs from the script properly, whereas TPccminer 2.2 does not work in the script yet. I'll keep playing around with it to see if some code in the script I added has an error. It's strange because the miner actually starts mining properly, but then errors out, rather than just not running at all which is normally how that goes.
I'll update with the results of a recompile with tpruvot's most recent ccminer release on 0018.
Thanks for keeping an eye on this.
EDIT: the latest tpruvot ccminer release runs at just about the same hashrate as krnlx within 1-2mh/s (463mh/s vs. 462mh/s) and in a 2 hour test it mined 26-27 coins an hour on sigt.pool.mn which is a small number more than I was mining before, but it's a shjort test length so I'll update again after 24 hours to get a better average. I was able to run tpruvot with skunk from command line in guake, but it crashes for some reason when running from the script almost immediately after it starts mining (before watchdog kicks in). Not sure why that's happening, the command line is the same in both as I have it configured.
In the end, I don't see a dramatic difference between the two miners' performance except that I know krnlx runs from the script properly, whereas TPccminer 2.2 does not work in the script yet. I'll keep playing around with it to see if some code in the script I added has an error. It's strange because the miner actually starts mining properly, but then errors out, rather than just not running at all which is normally how that goes.
Yeap skunk have sweet spot for every brand i think. U have to manage to find the fine tunning. I am not sure about this but i bet 1080ti can grab better performance on -i 26, i think u assign intensity per gpu like -d 0,1,2,3,4,5,6 -i 25 -d 7,8,9,10,11 -i 26
Anyway i get a bad experience with krnlx, before ccminer update, i was thinking about going back to palginmod with -20% hashrate ( not the new one )
I try to fix my variation GPU volatility, i cant run watchdog without lot of reboot by GPU sometime go to 0% for 1 second, everything is fine but watchdog dont like this
When u try to reboot miner via quake, i dont know why but on ccminer build, script cant kill "irq" is state in zombie mode. So when u launch miner again, GPU cant assign correct value cause if this "irq" zombie, just do "sudo pkill -e irq" and u can launch it
Are you using the newest watchdog; the one from the purple download link on the OP?