CCminer(SP-MOD) Modded GPU kernels.

[sp_]

Yea you can expect to realistically get about 19.5 Mh out of SP Bitcore. The intensity is way too high and it crashes constantly to get the hash SP is talking about.

I get 20MHASH with 80% tdp. 20% less power-> 10% less hash. I don't have problems with crashes in the latest builds. Running fine on 6x 1070 rigs...

[beecrp2]

Can anybody tell hashrate bitcore sp-mod on 1060 mining cards and 1060 3Gb?

[thin]

Can anybody tell hashrate bitcore sp-mod on 1060 mining cards and 1060 3Gb?

which one ) , there is mod2 and mod4 most popular )

[beecrp2]

Can anybody tell hashrate bitcore sp-mod on 1060 mining cards and 1060 3Gb?

which one ) , there is mod2 and mod4 most popular )

both ((=

[sp_]

The 1060 3gb can do 13.5-14 mhash++. 1060 6gb is normally around 10% faster. 14-15 MHASH
If you run with reduced tdp, f.ex 80% you loose around 10% hash. 12.5MHASH 1060 3gb

[beecrp2]

The 1060 3gb can do 14 mhash++. 1060 6gb is normally around 10% faster. 14-15 MHASH
If you run with reduced tdp, f.ex 80% you loose around 10% hash. 12.5MHASH 1060 3gb

Thx sp_!

[beecrp2]

sp_ is there any gpu limitations? ie more than 8 gpu mining is possible?

[sp_]

16 gpu's supported in sp-mod #4

[bensam1231]

What's the reason for me to do that? To mine your devfee? )

To increase your profit. Do you want a 35MHASH bitcore miner? Or do you want a 31MHASH bitcore miner?
The point is that #4 is faster, but it use more power and you need to run with the correct launch configuration.

The point is that it could be faster if you burn your card.

You have no idea what you're talking about, punctuated by 'burning your card'. TDP is what you're looking for if you want to reduce the load on the cards, not intensity. That's independent of intensity. There is nothing wrong with miners that use more power. If you don't like it, you reduce your TDP. That's your choice.
Intensities between #2 and #3/4 for Bitcore SP is indeed different and not because he's just increasing the intensity. Workable intensity in #4 is -i 22, higher then that causes random crashing even at stock clocks and highest TDPs.

The net difference between #2 and #4 is about 7%, minus a 2% devfee. So it's about 5% faster at stable intensities.

No it doesn't have anything to do with power delivery, I've mined on more demanding algos, such as Nexus and SIB. It has something to do with the fluctuating GPU loads (probably due to the algo) that causes your gpu clock thrashing So depending on how well your card is factory OC'd it can indeed crash on the default intensity with your miner SP. I have enough cards to know certain models will crash and some wont at those intensities. No matter what you adjust the clocks to unless you underclock, they will crash.

Open afterburner and watch the stats. That's also why the hashrate goes up and down as it cycles through the algos.

Bitcore when it was first implemented was a band aid fix in order to get it up and running, I don't think it really ever got past that point. There was a LOT of initial crashing when the algo was first implemented.

[sp_]

Workable intensity in #4 is -i 22, higher then that causes random crashing even at stock clocks and highest TDPs.

All my rigs use the default intensities without crashing. (windows 8/7 32gb virtual memory)
Could it be a windows 10 issue?

[abudfv2008]

What's the reason for me to do that? To mine your devfee? )

To increase your profit. Do you want a 35MHASH bitcore miner? Or do you want a 31MHASH bitcore miner?
The point is that #4 is faster, but it use more power and you need to run with the correct launch configuration.

The point is that it could be faster if you burn your card.

You have no idea what you're talking about, punctuated by 'burning your card'. TDP is what you're looking for if you want to reduce the load on the cards, not intensity. That's independent of intensity. There is nothing wrong with miners that use more power. If you don't like it, you reduce your TDP. That's your choice.
Intensities between #2 and #3/4 for Bitcore SP is indeed different and not because he's just increasing the intensity. Workable intensity in #4 is -i 22, higher then that causes random crashing even at stock clocks and highest TDPs.

The net difference between #2 and #4 is about 7%, minus a 2% devfee. So it's about 5% faster at stable intensities.

No it doesn't have anything to do with power delivery, I've mined on more demanding algos, such as Nexus and SIB. It has something to do with the fluctuating GPU loads (probably due to the algo) that causes your gpu clock thrashing So depending on how well your card is factory OC'd it can indeed crash on the default intensity with your miner SP. I have enough cards to know certain models will crash and some wont at those intensities. No matter what you adjust the clocks to unless you underclock, they will crash.

Open afterburner and watch the stats. That's also why the hashrate goes up and down as it cycles through the algos.

Bitcore when it was first implemented was a band aid fix in order to get it up and running, I don't think it really ever got past that point. There was a LOT of initial crashing when the algo was first implemented.

I definetly have idea.
What I have with sp4.
With 1080 and OC that I mentioned above. SP4 crashes with i22+. It is more or less stable at i20. But at that intencity it gives less result than sp2. 22 vs 24
1080ti with sp4 makes 30-30.5 on i25 vs 29-29.5 with sp2 on i20. Same OC settings.
1070 sp4 18.5-18.8 -i20 vs 18.8-19.5 sp2 i20
So it is clear that on the same intensity sp4 is worse than sp2. You can get extra 3-4% by rising intensity but loose at least the same by devfee.
That's because 5min devfee is taken first, so after every crash or change you will actually loose much more. As always liar sp_ is calling it 2% devfee while it is not.

[sp_]

1070 sp4 18.5-18.8 -i20 vs 18.8-19.5 sp2 i20

sp-mod #4 test with different intensities: gigabyte g1 gaming 100% tdp and mild oc (core and memory)

-i 20: 18.64 MHASH
-i 22: 20.50 MHASH (+9,9%)
-i 24.7998 (default): 21.14MHASH (+13.4%)

So don't run with intensity 20 because you get 13.4% more hash if you run without the -i in the batfile

I don't get crashes on my rigs.
Wich drivers are you using and operating system?
Try to run the miner at default intensity without any oc and 100% tdp. (stock settings.) does it still crash?

screenshot:

[wacko]

Yes I know that. The problem is that it can be done if you have 1-2 rig. But if you have 10-20-100, then you won't do that. May be there is some way to spread setting to all cards?

It can be done with any number of rigs, the principle is exactly the same as with any other way of GPU tuning. "Making" a curve takes me about 30 seconds, while setting +xxx clocks and -% powerlimit takes ~ 10 seconds. Then you test the card(s) as usual. On average it takes ~ 5-10 adjustments per card, so 150-300 seconds vs 50-100 seconds. Not that big of a deal even if you have 100 rigs 8 cards each. Will only take a few days to go through all of them. It all boils down to how much your time's worth. I don't have that many rigs and with curves I get more out of the cards since I can push them further (because the clocks/voltages don't fluctuate as much as they do with +/- xxx kind of tuning, so I don't have to leave nearly as much of a leeway).

[abudfv2008]

Yes I know that. The problem is that it can be done if you have 1-2 rig. But if you have 10-20-100, then you won't do that. May be there is some way to spread setting to all cards?

It can be done with any number of rigs, the principle is exactly the same as with any other way of GPU tuning. "Making" a curve takes me about 30 seconds, while setting +xxx clocks and -% powerlimit takes ~ 10 seconds. Then you test the card(s) as usual. On average it takes ~ 5-10 adjustments per card, so 150-300 seconds vs 50-100 seconds. Not that big of a deal even if you have 100 rigs 8 cards each. Will only take a few days to go through all of them. It all boils down to how much your time's worth. I don't have that many rigs and with curves I get more out of the cards since I can push them further (because the clocks/voltages don't fluctuate as much as they do with +/- xxx kind of tuning, so I don't have to leave nearly as much of a leeway).

You can talk fairy tales about 30 seconds to someone else. It is 3 clicks and vs several dosen . But anyway it is possible to set curve and really save it and spread on other cards by editing file directly.

[abudfv2008]

1070 sp4 18.5-18.8 -i20 vs 18.8-19.5 sp2 i20

sp-mod #4 test with different intensities: gigabyte g1 gaming 100% tdp and mild oc (core and memory)

-i 20: 18.64 MHASH
-i 22: 20.50 MHASH (+9,9%)
-i 24.7998 (default): 21.14MHASH (+13.4%)

So don't run with intensity 20 because you get 13.4% more hash if you run without the -i in the batfile

I don't get crashes on my rigs.
Wich drivers are you using and operating system?
Try to run the miner at default intensity without any oc and 100% tdp. (stock settings.) does it still crash?

As I said before sp4 on 1080ti with i25 on same settings is only 3-4% faster then sp2.
On same intensities sp4 is worse than sp2. But yes it is capable of running on higher intensities... but as with my 1080 rig I need to lower OC in order to make it work. Which leads to even less advantage.
So taking insane 5minutes devfee into account at the start sp4 will make less for the miner.

[wacko]

You can talk fairy tales about 30 seconds to someone else. It is 3 clicks and vs several dosen . But anyway it is possible to set curve and really save it and spread on other cards by editing file directly.

If it takes you a lot more than 30 seconds then you're doing it wrong. With curves in MSI AB all you need to do is set one point precisely, smth like 1911@0.85V. All the other points you just drag superfast down to random clocks, it doesn't matter which, they simply all need to be lower than the only clock you actually set. Then you hit "apply" and your curve is automatically made straight by the program. I've just done it with one of my cards in the test rig, and it took me ~ 30 seconds. Again, if it takes you a lot more than you're either doing it wrong or might want to learn how to handle a mouse. I mean, there's plenty of people out there who actually drag all the points to make a straight line or something. That takes a lot of time and is completely unnecessary.

As to applying the same curve to different cards — I don't know whether it's possible. Doesn't make much sense to me since all the cards are different and curves are by their nature designed for precise tuning of each card. Those that don't care about this kind of precision might just go with +/- clocks/limit adjustment, which can be synced between all the cards in the rig.

[Kompik]

You can talk fairy tales about 30 seconds to someone else. It is 3 clicks and vs several dosen . But anyway it is possible to set curve and really save it and spread on other cards by editing file directly.

If it takes you a lot more than 30 seconds then you're doing it wrong. With curves in MSI AB all you need to do is set one point precisely, smth like 1911@0.85V. All the other points you just drag superfast down to random clocks, it doesn't matter which, they simply all need to be lower than the only clock you actually set. Then you hit "apply" and your curve is automatically made straight by the program. I've just done it with one of my cards in the test rig, and it took me ~ 30 seconds. Again, if it takes you a lot more than you're either doing it wrong or might want to learn how to handle a mouse. I mean, there's plenty of people out there who actually drag all the points to make a straight line or something. That takes a lot of time and is completely unnecessary.

As to applying the same curve to different cards — I don't know whether it's possible. Doesn't make much sense to me since all the cards are different and curves are by their nature designed for precise tuning of each card. Those that don't care about this kind of precision might just go with +/- clocks/limit adjustment, which can be synced between all the cards in the rig.

Still this is only manageble if you mine one algo. I for example switch coins couple times a week and dont remember when I was mining the same coin for 14 days. Each algo stresses your card differently so the curves are not transferable unless you set it really low which kind of nulifies the effort.

[wacko]

Still this is only manageble if you mine one algo. I for example switch coins couple times a week and dont remember when I was mining the same coin for 14 days. Each algo stresses your card differently so the curves are not transferable unless you set it really low which kind of nulifies the effort.

I don't mine one algo. There are 5 "slots" for different profiles in MSI AB. I have a different set of curves saved for each slot. All it takes is just to select a different profile before switching to another algo.

[abudfv2008]

Still this is only manageble if you mine one algo. I for example switch coins couple times a week and dont remember when I was mining the same coin for 14 days. Each algo stresses your card differently so the curves are not transferable unless you set it really low which kind of nulifies the effort.

I don't mine one algo. There are 5 "slots" for different profiles in MSI AB. I have a different set of curves saved for each slot. All it takes is just to select a different profile before switching to another algo.

And here we come to the problem of many rigs. You need to remember each profile, each algo it is capable running with etc. You have 5 profiles at least 4 types of rigs and ~20 algos.
That's why it is impossible if you switch coins frequently and have many rigs.
I just set maximum OC that is capable of mining all algos without need to change OC.
Yes if sometimes I mine some coin for rather long period I finetune the OC.

[sp_]

On same intensities sp4 is worse than sp2.

Open gpuz and check the memory usage of the two exe files.
SP2 is using more memory than SP4 on the same intensity setting.
This meens that if you use SP4  you need to increase the intensity to have the same memory usage as SP2.

Comparing the intensities between two kernels with different memory multipliers is a waste of time... As you can see in my example, the default intensity setting of the sp-mod #4 on the gtx 1070 give you 13.4% more hash than running with -i 20.