CCminer(SP-MOD) Modded GPU kernels.

[dominuspro]

I was mining ETH earlier with 750Ti:s on linux and the cards hashed at around 7-8Mhs back then.

Maybe You forgot to OC  Memory should be overclocked too for ETH(especially 750ti). I was hashing at 21+MH with 2x750ti.

I should do some tests again... Never tried other maxwells in linux. Maybe I'll find some time around wednesday...

BTW what should be the --diff for FTC solo mining? Default settings in r.74 gets accepted 4/10 blocks.

[bathrobehero]

Seems some more Hashes for each gpu. But non profitable nowadays  

Seems like Etherum is the only profitable algo at the moment on the NVIDIA unreleased gpu's

I'm not sure about that. Anybody know how much a 750 Ti is expected to earn a day (before electricity)?

The 750ti is not good in mining etherum. You need a compute 5.2 or bether.

Period   ETH   USD
Minute   0.000342   $0.00
Hour   0.020540   $0.02
Day   0.492959   $0.39
Week   3.450715   $2.73
Month   14.788778   $11.71
Notes

Thanks. How about 970s?

http://etherscan.io/ether-mining-calculator

Check by yourself I allways got a correct calculation.
750ti was doing 8-11MH some time ago in linux.
Don't know if it degraded allready...

970 should be around 20MH.

That's exactly why I asked because a couple months ago all the profit calc sites were way off, showing much more profit than it really was.

BTW what should be the --diff for FTC solo mining? Default settings in r.74 gets accepted 4/10 blocks.

Depends on the pool. If there are rejects (low diff shares) then decrease the diff multiplier below 1.0 and if a pool shows low hashrates without rejects then increasing -f is a good place to start.

[Cryptozillah]

I was mining ETH earlier with 750Ti:s on linux and the cards hashed at around 7-8Mhs back then.

Maybe You forgot to OC  Memory should be overclocked too for ETH(especially 750ti). I was hashing at 21+MH with 2x750ti.

I should do some tests again... Never tried other maxwells in linux. Maybe I'll find some time around wednesday...

BTW what should be the --diff for FTC solo mining? Default settings in r.74 gets accepted 4/10 blocks.

I had to check again in old logs and i remembered it wrong. My cards where running around 10Mhs unclocked. They are factory oc:d a bit though. Never oc:d memory while i was mining ETH.

[Genoil]

With the current difficulty and price etherum is minable on the 750ti. (9 MHASH)

50watt *24 hours. 1,2Kwh

66% profit with a powercost of $0.1 per KWh.

I've heard from several ETH miners using 750Ti that hashrate has already dropped significantly, like on Windows (because of TLB trashing). It's more like 4MH now...

[chrysophylax]

With the current difficulty and price etherum is minable on the 750ti. (9 MHASH)

50watt *24 hours. 1,2Kwh

66% profit with a powercost of $0.1 per KWh.

I've heard from several ETH miners using 750Ti that hashrate has already dropped significantly, like on Windows (because of TLB trashing). It's more like 4MH now...

im about to compile and test on the test system - and see how it runs ...

fedora 22 x64 c7.5 - and stock clocks ... gigabyte 750ti oc lp ...

if i ever get to the office today ...

im following your instructions on your git genoil ...

trying to get it done on ssh now - but very limited with all the security i deal with on my network ...

edit - json compile breaks ...

#crysx

[dominuspro]

BTW what should be the --diff for FTC solo mining? Default settings in r.74 gets accepted 4/10 blocks.

Depends on the pool. If there are rejects (low diff shares) then decrease the diff multiplier below 1.0 and if a pool shows low hashrates without rejects then increasing -f is a good place to start.

Asking about solo mining... diff 2 seems even worst:

Code:

[2015-12-10 22:40:47] GPU #0: GeForce GTX 980, 676
[2015-12-10 22:40:47] accepted: 0/3 (0.00%), 2496 kH/s nooooo
[2015-12-10 22:41:11] GPU #4: GeForce GTX 970, 606
[2015-12-10 22:41:12] GPU #3: GeForce GTX 970, 606
[2015-12-10 22:41:12] GPU #2: GeForce GTX 970, 636
[2015-12-10 22:41:16] GPU #0: GeForce GTX 980, 686
[2015-12-10 22:41:17] GPU #3: GeForce GTX 970, 605
[2015-12-10 22:41:17] GPU #2: GeForce GTX 970, 633
[2015-12-10 22:41:17] GPU #4: GeForce GTX 970, 604
[2015-12-10 22:41:47] GPU #3: GeForce GTX 970, 604
[2015-12-10 22:41:47] GPU #2: GeForce GTX 970, 633
[2015-12-10 22:41:47] GPU #4: GeForce GTX 970, 604
[2015-12-10 22:42:05] GPU #0: GeForce GTX 980, 684
[2015-12-10 22:42:16] GPU #3: GeForce GTX 970, 605
[2015-12-10 22:42:17] GPU #2: GeForce GTX 970, 633
[2015-12-10 22:42:17] GPU #4: GeForce GTX 970, 604
[2015-12-10 22:42:17] GPU #0: GeForce GTX 980, 684
[2015-12-10 22:42:46] GPU #2: GeForce GTX 970, 634
[2015-12-10 22:42:47] GPU #4: GeForce GTX 970, 604
[2015-12-10 22:42:47] GPU #0: GeForce GTX 980, 684
[2015-12-10 22:43:08] GPU #4: GeForce GTX 970, 603
[2015-12-10 22:43:08] accepted: 0/4 (0.00%), 2508 kH/s nooooo

Now trying diff 0.5
And runing ccminer.exe -a neoscrypt -o IP:port -u x -p y --broken-neo-wallet -d 0,2,3,4 --diff 0.5

[bathrobehero]

BTW what should be the --diff for FTC solo mining? Default settings in r.74 gets accepted 4/10 blocks.

Depends on the pool. If there are rejects (low diff shares) then decrease the diff multiplier below 1.0 and if a pool shows low hashrates without rejects then increasing -f is a good place to start.

Asking about solo mining... diff 2 seems even worst:

Code:

[2015-12-10 22:40:47] GPU #0: GeForce GTX 980, 676
[2015-12-10 22:40:47] accepted: 0/3 (0.00%), 2496 kH/s nooooo
[2015-12-10 22:41:11] GPU #4: GeForce GTX 970, 606
[2015-12-10 22:41:12] GPU #3: GeForce GTX 970, 606
[2015-12-10 22:41:12] GPU #2: GeForce GTX 970, 636
[2015-12-10 22:41:16] GPU #0: GeForce GTX 980, 686
[2015-12-10 22:41:17] GPU #3: GeForce GTX 970, 605
[2015-12-10 22:41:17] GPU #2: GeForce GTX 970, 633
[2015-12-10 22:41:17] GPU #4: GeForce GTX 970, 604
[2015-12-10 22:41:47] GPU #3: GeForce GTX 970, 604
[2015-12-10 22:41:47] GPU #2: GeForce GTX 970, 633
[2015-12-10 22:41:47] GPU #4: GeForce GTX 970, 604
[2015-12-10 22:42:05] GPU #0: GeForce GTX 980, 684
[2015-12-10 22:42:16] GPU #3: GeForce GTX 970, 605
[2015-12-10 22:42:17] GPU #2: GeForce GTX 970, 633
[2015-12-10 22:42:17] GPU #4: GeForce GTX 970, 604
[2015-12-10 22:42:17] GPU #0: GeForce GTX 980, 684
[2015-12-10 22:42:46] GPU #2: GeForce GTX 970, 634
[2015-12-10 22:42:47] GPU #4: GeForce GTX 970, 604
[2015-12-10 22:42:47] GPU #0: GeForce GTX 980, 684
[2015-12-10 22:43:08] GPU #4: GeForce GTX 970, 603
[2015-12-10 22:43:08] accepted: 0/4 (0.00%), 2508 kH/s nooooo

Now trying diff 0.5
And runing ccminer.exe -a neoscrypt -o IP:port -u x -p y --broken-neo-wallet -d 0,2,3,4 --diff 0.5

The diff parameter doesn't matter for solomining at all (sorry, missed that you said solo). Using wallet 0.8.7.1 I have no issues solomining (found a block while writing this). Also, you shouldn't be able to find shares (reject or not) anywhere near that frequently with that hashrate.
In fact, a 5 card 970 rig (ignoring the 980 for simplicity) have an average block finding frequency of 36 minutes with the current difficulty. It's like you're mining to another wallet that's not FTC. Or your wallet have sync issues.

[chrysophylax]

hi all ...

i just wanted to know if anyone uses a configuration file for ccminer ...

if you do - what is the actual format of the .conf file and what structure should it take ( i know its in json format - but how is it done? ) ...

i have been using full commandline executions for as long as i can remember - and now im starting to automate the entire farm through cron / file / systemd ( and eventually through web interface ) ... this is taking me a long time - and then i realized i could use .conf files to set ccminer to run different commands at different times ...

anyway - if anyone could help - that would be great ... even with a couple of examples of the .conf files that could be written in different ways ...

it would be very much appreciated ...

tanx ...

#crysx

[scryptr]

hi all ...

i just wanted to know if anyone uses a configuration file for ccminer ...

if you do - what is the actual format of the .conf file and what structure should it take ( i know its in json format - but how is it done? ) ...

i have been using full commandline executions for as long as i can remember - and now im starting to automate the entire farm through cron / file / systemd ( and eventually through web interface ) ... this is taking me a long time - and then i realized i could use .conf files to set ccminer to run different commands at different times ...

anyway - if anyone could help - that would be great ... even with a couple of examples of the .conf files that could be written in different ways ...

it would be very much appreciated ...

tanx ...

#crysx

JSON.CONF--

The following is a simplified example:

=====cut line======

{
   "url" : "stratum+tcp://stratum.nicehash.com:3345",
   "user" : "BTCaddyhere.wrkr1",
   "pass" : "x",

   "algo" : "quark",
   "intensity" : "23.7",
      
   "api-bind" : "127.0.0.1:4068",
   "statsavg" : 20,
   "quiet" : false,
   "debug" : false,
   "protocol" : false
}

======cut line=====

Save it as "name.conf".  In Linux, use this command line to call it:

./ccminer -c name.conf

You can add parameters, like cpu mining and cpu priority, and I generally execute the command line in a BASH file with environment parameters.  I've given a number of examples for solo-mining in this thread.

--scryptr

[dominuspro]

BTW what should be the --diff for FTC solo mining? Default settings in r.74 gets accepted 4/10 blocks.

Depends on the pool. If there are rejects (low diff shares) then decrease the diff multiplier below 1.0 and if a pool shows low hashrates without rejects then increasing -f is a good place to start.

Asking about solo mining... diff 2 seems even worst:

Code:

[2015-12-10 22:40:47] GPU #0: GeForce GTX 980, 676
[2015-12-10 22:40:47] accepted: 0/3 (0.00%), 2496 kH/s nooooo
[2015-12-10 22:41:11] GPU #4: GeForce GTX 970, 606
[2015-12-10 22:41:12] GPU #3: GeForce GTX 970, 606
[2015-12-10 22:41:12] GPU #2: GeForce GTX 970, 636
[2015-12-10 22:41:16] GPU #0: GeForce GTX 980, 686
[2015-12-10 22:41:17] GPU #3: GeForce GTX 970, 605
[2015-12-10 22:41:17] GPU #2: GeForce GTX 970, 633
[2015-12-10 22:41:17] GPU #4: GeForce GTX 970, 604
[2015-12-10 22:41:47] GPU #3: GeForce GTX 970, 604
[2015-12-10 22:41:47] GPU #2: GeForce GTX 970, 633
[2015-12-10 22:41:47] GPU #4: GeForce GTX 970, 604
[2015-12-10 22:42:05] GPU #0: GeForce GTX 980, 684
[2015-12-10 22:42:16] GPU #3: GeForce GTX 970, 605
[2015-12-10 22:42:17] GPU #2: GeForce GTX 970, 633
[2015-12-10 22:42:17] GPU #4: GeForce GTX 970, 604
[2015-12-10 22:42:17] GPU #0: GeForce GTX 980, 684
[2015-12-10 22:42:46] GPU #2: GeForce GTX 970, 634
[2015-12-10 22:42:47] GPU #4: GeForce GTX 970, 604
[2015-12-10 22:42:47] GPU #0: GeForce GTX 980, 684
[2015-12-10 22:43:08] GPU #4: GeForce GTX 970, 603
[2015-12-10 22:43:08] accepted: 0/4 (0.00%), 2508 kH/s nooooo

Now trying diff 0.5
And runing ccminer.exe -a neoscrypt -o IP:port -u x -p y --broken-neo-wallet -d 0,2,3,4 --diff 0.5

The diff parameter doesn't matter for solomining at all (sorry, missed that you said solo). Using wallet 0.8.7.1 I have no issues solomining (found a block while writing this). Also, you shouldn't be able to find shares (reject or not) anywhere near that frequently with that hashrate.
In fact, a 5 card 970 rig (ignoring the 980 for simplicity) have an average block finding frequency of 36 minutes with the current difficulty. It's like you're mining to another wallet that's not FTC. Or your wallet have sync issues.

Are You using release 74?
I'm using the same wallet but I get more non accepted shares then good ones. Overnight I got accepted 4/27. Not sure about the diff. It looks worst if I use it with factors 0.5 and 2.
I'll do another, longer run without it...

[chrysophylax]

hi all ...

i just wanted to know if anyone uses a configuration file for ccminer ...

if you do - what is the actual format of the .conf file and what structure should it take ( i know its in json format - but how is it done? ) ...

i have been using full commandline executions for as long as i can remember - and now im starting to automate the entire farm through cron / file / systemd ( and eventually through web interface ) ... this is taking me a long time - and then i realized i could use .conf files to set ccminer to run different commands at different times ...

anyway - if anyone could help - that would be great ... even with a couple of examples of the .conf files that could be written in different ways ...

it would be very much appreciated ...

tanx ...

#crysx

JSON.CONF--

The following is a simplified example:

=====cut line======

{
   "url" : "stratum+tcp://stratum.nicehash.com:3345",
   "user" : "BTCaddyhere.wrkr1",
   "pass" : "x",

   "algo" : "quark",
   "intensity" : "23.7",
      
   "api-bind" : "127.0.0.1:4068",
   "statsavg" : 20,
   "quiet" : false,
   "debug" : false,
   "protocol" : false
}

======cut line=====

Save it as "name.conf".  In Linux, use this command line to call it:

./ccminer -c name.conf

You can add parameters, like cpu mining and cpu priority, and I generally execute the command line in a BASH file with environment parameters.  I've given a number of examples for solo-mining in this thread.

--scryptr

much appreciated scryptr ...

i am streamlining the donation servers by culling a lot of long methods - and shortcutting - as well as cleaning a few scripts and writing new scripts for mining as well as the stratum proxies ... which lead me to the is amazing revelation that ccminer uses .conf files all along ( DUH! ) ...

im fiddling with making ccminer a centralized miner and a service rather a commandline executable - with .conf files being the only internal file required ... the .conf file is the bit im really stuck on before i can do the rest and test ...

this should make thefarm as efficient as possible ...

which also lends itself to allow the creation of a management console that could allow changes ( and creation / deletion ) of the .conf files using a web interface for the entire farm - instead of being changed individually ...

i have also looked at you script that you wrote a while back - and will be changing a few things in it to make it a little more uptodate and adjusted to what the farm is doing ... your help with this would be very much appreciated ... im actually perplexed why you havent worked on that script further - it seems to be logically sound ...

this script could also be the thing that activates / deactivates the miner on the various .conf files ... but i have yet to get my head around how that could work ...

tanx for the .conf layout though mate ... that is a great help ...

#crysx

[sp_]

I have another optimalization in the quark algo. If you want it opensource please donate.
The weekend is comming and I need beer

Cuda 7.5 seems to perform bether in most algos with the correct tuning. Chrx: did you try to compile the latest git? How is it performing on linux? x11/x13/qubit

[sp_]

Submitted a tiny speedup in the quark algo. A teaser
+200KHASH on the gtx 970

Where are my donations?

[chrysophylax]

I have another optimalization in the quark algo. If you want it opensource please donate.
The weekend is comming and I need beer

Cuda 7.5 seems to perform bether in most algos with the correct tuning. Chrx: did you try to compile the latest git? How is it performing on linux? x11/x13/qubit

i have mate - and i can tell you - just from the test machine its a nice chunk of hash increase ...

across thefarm - it should do nice ...

but that extra teaser for quark ... damn - if i wasnt sick - i would have already been in the office ... all of this stuff ( including the wallets and mining ) is under lock and key since the last ddos killed two of my servers and one of my vps almost got hacked ( about 16000 attempts on cracking the password in the last 48 hours ) ... so i maintain a tight ship now - and have to physically be there to get a lot of the things done ...

but i said i would put a miner to hash for you - and i will ... should be at least a beer or two in that ...

cuda 7.5 was working fine in fedora 22 x64 - as discussed previously - but im upgrading the test machine ( only one of two machines off the network - the other machine is an amd one for wolf0 ) and will try and get a compile and see how it runs when it finishes a fedora 23 x64 c7.5 upgrade ...

this nvidia test machine has 3 x gigabyte 750ti oc lp cards in it - stock ... so will luv to see more that 2800kh x11 and 5890kh quark on those cards ...

25min tests should show how they go after the upgrade - but will have to get that done tomorrow now ...

sp - still mulling over the eth kernel? ... or making it an inclusion in to ccminer-spmod76? ... ...

ive just tried following the compile directions and compile dies everywhere - mainly for llvm version conflicts in fedora 22 x64 ... but there could be much more issues ... apparently tested on fedora 23 x64 - i would like to try that when the fedora 23 x64 upgrade finishes ...

first to test with the new fedora 23 x64 c7.5 - ccminer-spmod75 tomorrow ...

tanx for the update sp ... cant wait to compile and see ...

#crysx

[sp_]

More cuda 7.5 modding and recoding

-Faster quark
-Faster qubit
-Faster x11
-Faster x13
-Faster x14
-Faster x15


1.5.76(sp-MOD) is available here: (11-dec-2015)

https://github.com/sp-hash/ccminer/releases/

The sourcecode is available here:

https://github.com/sp-hash/ccminer

[sp_]

tanx for the update sp ... cant wait to compile and see ...

I just released 76 with increased hashrate all over the place. But some of the algos are still slower than release 74. Quark has the most boost this time, and mostly on compute 5.2 devices.

[chrysophylax]

tanx for the update sp ... cant wait to compile and see ...

I just released 76 with increased hashrate all over the place. But some of the algos are still slower than release 74. Quark has the most boost this time, and mostly on compute 5.2 devices.

ok great ...

then thats the first thing i will test when i get into the office tomorrow ...

a miner will hash quark on your donation address ( donate-sp.granitecoin.com ) and see how it tests ...

look out for the test on nicehash ( eu stratum ) ...

tanx again mate ... i hope it compiles and works well on the new system ...

#crysx

[sp_]

tanx for the update sp ... cant wait to compile and see ...

I just released 76 with increased hashrate all over the place. But some of the algos are still slower than release 74. Quark has the most boost this time, and mostly on compute 5.2 devices.

ok great ...
then thats the first thing i will test when i get into the office tomorrow ...
a miner will hash quark on your donation address ( donate-sp.granitecoin.com ) and see how it tests ...
look out for the test on nicehash ( eu stratum ) ...
tanx again mate ... i hope it compiles and works well on the new system ...
#crysx

Just tested quark release 76 on my 980ti g1 gigabyte windforce oc.
27.3 (+1,4MHASH) on the standard clocks(New WORLD RECORD)!
Release 74 is only doing 25.9MHASH.

On the EVGA SSC gtx 960. 11 MHASH on standard clocks. up 0.5 MHASH from release 74

[pallas]

More cuda 7.5 modding and recoding

-Faster quark
-Faster qubit
-Faster x11
-Faster x13
-Faster x14
-Faster x15


1.5.76(sp-MOD) is available here: (11-dec-2015)

https://github.com/sp-hash/ccminer/releases/

The sourcecode is available here:

https://github.com/sp-hash/ccminer

Thanks very much sp_!
I'm sad as I currently am unable to test or work on it, but I hope to be able to give it a chance during the weekend.

[sp_]

Guys, I have published 5% faster quark kernal for free and only recieved 0.05BTC in donations.

Do you want a continued opensource developement and a faster hashrate?
Or do I have to sell private kernals?
To keep the business profitable you need to support the developent.
0.01BTC from each of you would be nice.