CCminer(SP-MOD) Modded GPU kernels.

[thinkfar]

Bitcore is trading at $41 $48 I wouldn't be surprised if the value rise to $150 (bitcoin gold).

Already down to 32$.

[Ryuh]

Hey guys, what is the hashrate of bitcore on 1070 with sp mod?

EDIT: Sorry, had to read the full post first. It says 21.5 Mh/s is that correct?

[sp_]

no its not true...
normal hash in 1070 with sp mod - 19,5-20 mh....  

21.5 mh - pl - 100-110> max core and max memory. and more watts per card

Sp-mod #4 is peaking at 22.2 MHASH on the gigabyte g1 gaming with 100% tdp and oc. (micron memory)

[garytheasshole]

no its not true...
normal hash in 1070 with sp mod - 19,5-20 mh....  

21.5 mh - pl - 100-110> max core and max memory. and more watts per card

Sp-mod #4 is peaking at 22.2 MHASH on the gigabyte g1 gaming with 100% tdp and oc. (micron memory)

Don't forget to mention your 2% fee on top of your "donation"

[thevictimofuktyranny]

Have you seen this SP_

mkxminer: optimized Lyra2rev2 miner for AMD GPUs (Vertcoin, Monacoin, XVG)

Radeon Pro Duo: 84.8MHs (42.4 + 42.4)
Fury X: 55MHs
Vega56: 47MHs (can be optimised further, just need some time and incentive)
RX 580: 39MHs
RX 480: 36MHs
R9 390: 32MHs
R9 380X: 26MHs
R9 280X: 26MHs

[bensam1231]

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.

[Oakey22]

bitcore is one of the coins that is going to drop very soon, not worth mining and especially with the SP-MOD that crashes if you even look at it

[sp_]

sp-mod #1 and #2 are unstable and not supported anymore. #3 and #4 are working fine. Bitcore is using more power than other algos so you need powered risers and bigger psu's. If not you need to run at reduced tdp and intensity, and then you loose hashrate..

[miner32342]

blake2s sp-mod

since the developer abandoned this mod, I ask to share it, if not difficult

[sp_]

blake2s is not abandoned

[miner32342]

blake2s is not abandoned

it's just that you have it crossed out

[abudfv2008]

sp-mod #1 and #2 are unstable and not supported anymore. #3 and #4 are working fine. Bitcore is using more power than other algos so you need powered risers and bigger psu's. If not you need to run at reduced tdp and intensity, and then you loose hashrate..

Something is very wrong with your statements
sp2 => TDP95 ~2000/5054 -i 20 6*1080 = 145Mh/s
sp4 => same OC and -i 20 6*1080 = 135Mh/s - devfee.

[sp_]

Something is very wrong with your statements
sp2 => TDP95 ~2000/5054 -i 20 6*1080 = 145Mh/s
sp4 => same OC and -i 20 6*1080 = 135Mh/s - devfee.

The intensities has changed in sp4. (memory usage has been reduced in the kernel code) To run at full speed You need to run with -i 25 and not -i 20. sp4 also need alot of oc on the memory. -500 on mem is slow. +750 is good.

[abudfv2008]

Something is very wrong with your statements
sp2 => TDP95 ~2000/5054 -i 20 6*1080 = 145Mh/s
sp4 => same OC and -i 20 6*1080 = 135Mh/s - devfee.

The intensities has changed in sp4. (memory usage has been reduced in the kernel code) To run at full speed You need to run with -i 25 and not -i 20. sp4 also need alot of oc on the memory. -500 on mem is slow. +750 is good.

With the same settings and even -i 22 the system goes to reboot after some shares.
Thats because ridiculous frequency changes - even 1568-2164 is reached sometimes.
But these OC are used for all other algos and miners and works perfectly.

[sp_]

Thats because ridiculous frequency changes - even 1568-2164 is reached sometimes.
But these OC are used for all other algos and miners and works perfectly.

every algo needs to be tuned differently.

You need to find out why your card is trottleing. Open gpuz and check the perfCap reason. Reboots and freezes is often caused by lack of power or missing powered risers, or that you have to many powered risers on the same cable in the psu. Tune the rig with one card first. Then add more cards later.

[abudfv2008]

Thats because ridiculous frequency changes - even 1568-2164 is reached sometimes.
But these OC are used for all other algos and miners and works perfectly.

every algo needs to be tuned differently.

You need to find out why your card is trottleing. Open gpuz and check the perfCap reason. Reboots and freezes is often caused by lack of power or missing powered risers, or that you have to many powered risers on the same cable in the psu. Tune the kernel with one card first. Then add more cards later.

What's the reason for me to do that? To mine your devfee? )
No thanks - free sp2mod is better and faster. But it crashes on some rigs frequently.

[wacko]

With the same settings and even -i 22 the system goes to reboot after some shares.
Thats because ridiculous frequency changes - even 1568-2164 is reached sometimes.
But these OC are used for all other algos and miners and works perfectly.

That's why I don't overclock Pascal cards by simply inputting +xxx in clocks and setting the powerlimit. It's very easy but also very imprecise. Not to mention downright useless for discussing with other people (and SP regularly exploits it by not saying the actual clocks/voltages but only something like +200 MHz which makes it harder for other users to figure out when we try to assess the actual difference between the free miners and the paid sp mods). When you simply set the max powerlimit and +/- clocks, you allow the GPU to set the clocks and voltages however it sees fit — the only limit being the power limit / TDP. So voltage and clocks jump like crazy, especially with algos like timetravel10.

If you don't want it, adjust these parameters with curves (msi ab and evga precision have this functionality). With curves you have complete control over clocks and voltages. It's more time-consuming to figure out the stable clocks for each card/algo, but a lot more predictable as well since the card will stay at the clock/voltage pair that you set.

[sp_]

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.

[abudfv2008]

With the same settings and even -i 22 the system goes to reboot after some shares.
Thats because ridiculous frequency changes - even 1568-2164 is reached sometimes.
But these OC are used for all other algos and miners and works perfectly.

That's why I don't overclock Pascal cards by simply inputting +xxx in clocks and setting the powerlimit. It's very easy but also very imprecise. Not to mention downright useless for discussing with other people (and SP regularly exploits it by not saying the actual clocks/voltages but only something like +200 MHz which makes it harder for other users to figure out when we try to assess the actual difference between the free miners and the paid sp mods). When you simply set the max powerlimit and +/- clocks, you allow the GPU to set the clocks and voltages however it sees fit — the only limit being the power limit / TDP. So voltage and clocks jump like crazy, especially with algos like timetravel10.

If you don't want it, adjust these parameters with curves (msi ab and evga precision have this functionality). With curves you have complete control over clocks and voltages. It's more time-consuming to figure out the stable clocks for each card/algo, but a lot more predictable as well since the card will stay at the clock/voltage pair that you set.

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?

[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.