Author

Topic: [ANN] sgminer v5 - optimized X11/X13/NeoScrypt/Lyra2RE/etc. kernel-switch miner - page 193. (Read 877859 times)

hero member
Activity: 658
Merit: 500
ok i think i have the fix
modded the groestl.cl file a little and set #define SPH_LUFFA_PARALLEL 1, and re-enabled #include "aes_helper.cl"  in darkcoin-mod.cl
getting 6mh/s no real changes in the other algo's that i can see
darkcoin-mod.cl
https://www.dropbox.com/s/gqv2m7y62olfzbs/darkcoin-mod.cl
groestl.cl
https://www.dropbox.com/s/9ugaly2utnwbda2/groestl.cl
EDIT: there is still a little something different as i am only getting 5.96 instead of the 6.04 i was getting with the other kernel
sr. member
Activity: 547
Merit: 250
I'll have to try your bin after work bullus.

Maybe that's why I had 6 at start but dropped it, must've deleted it.

Can you link us also some marucoin-mod and bitblock bins from the same X15_AMD, worksize 64?
sr. member
Activity: 294
Merit: 250
hero member
Activity: 658
Merit: 500
Hey! Can some one confirm 280x perfomance?

My results with SGminer v5:
X11 - 3 mh/s
X13 - 2,5 mh/s
X15 - 2,3 mh/s
NIST5 - ?

With other miner, sph, i got:
X11- 4.1 mh/s
X13- 2,9mh/s

*EXPECTED* speed should be your Scrypt hash rate multiplied by 16. 

My 280x is 730 KH/s Scrypt, so NIST5 should be 730*16=11680 KH/s or 11.6 MH/s.

What about other speeds, low or normal?

You can find out a ballpark of what your expected hash rate should be by using these multipliers of your Scrypt hash rate:

Scrypt ---- *1
Scrypt-N - *.5
X11 ------- *5.5
X13 ------- *4
X15 ------- *3.5
Keccak --- *500
NIST5 ----- *16
Actually we are looking at fixes to make the hash rate *6 on x11 at least, don't know yet how it will affect x13, x14, and x15.
But it should increase those as well
full member
Activity: 142
Merit: 101
Hey! Can some one confirm 280x perfomance?

My results with SGminer v5:
X11 - 3 mh/s
X13 - 2,5 mh/s
X15 - 2,3 mh/s
NIST5 - ?

With other miner, sph, i got:
X11- 4.1 mh/s
X13- 2,9mh/s

*EXPECTED* speed should be your Scrypt hash rate multiplied by 16. 

My 280x is 730 KH/s Scrypt, so NIST5 should be 730*16=11680 KH/s or 11.6 MH/s.

What about other speeds, low or normal?

You can find out a ballpark of what your expected hash rate should be by using these multipliers of your Scrypt hash rate:

Scrypt ---- *1
Scrypt-N - *.5
X11 ------- *5.5
X13 ------- *4
X15 ------- *3.5
Keccak --- *500
NIST5 ----- *16
full member
Activity: 196
Merit: 100
Anybody working on p2pool?
If so, what version?
hero member
Activity: 546
Merit: 500
If you are getting sick cards, then most of the time it's simply too high memory clock or core clock, or cards running too hot.

Hook card up to a monitor, and run OCCT GPU stress test with error checking mode. Or you could use furmark which has similar features.

Run the card at the clocks you intend to mine at, using the most brutal shader/ram settings in those programs you can. This will reveal if the card is stable at the card's "maximum utilization" aka maximum power and heat that any miner algo could possibly throw at it.

Be sure to let the card temperature ramp up and equilibrate for some time, before judging if it's stable. If it's not, improve fanspeed and/or lower clocks.

Also something to keep in mind, with the new algos that use very little power, is on many cards you can undervolt the cards quite considerably. Because efficiency/clock speed is a non-linear relationship, you can find that for example a decrease in voltage of 10% will give a much greater than 10% improvement in efficiency. For some R9 270 cards for example, a 10% reduction in voltage will give about a 30% improvement in efficiency. This improvement is so dramatic because most of the R9 series is clocked at the factory right up to its stability limit anyway. tl;dr - unless you have free power its better to improve efficiency rather than striving for top-notch clock frequencies.
hero member
Activity: 658
Merit: 500
Nice, I don't have sick card, running for 10hours now.

I see u get about 200kh/s more with x13/x15, is it because of your higher memclock or because u change the cl for x13/x15? Otherwise can upload u your bin or cl?

I really wish I knew, I changed so much shit in the last 4 hours, I'm trying to find a stable rock before I go to sleep.

At 1050/1500 it ran but shit on itself when flipped algos; near the same for 1040/1400.  1040/1300 works on 2 rigs solid, but not 3rd.
1040/1300 and removing "disable ULPS" in MSI AB will not get you superhigh 5.9-6M hashrate, more like 5.6, but at least drivers hold.

It may have to do with MSI AB.

I don't think it's LUFFA...

I got the idea to sub the smaller groestl.cl in the folder, since all x[n] algos call for it, and it's the one that is most impacted by 14.6+
There's practically no change, except for lack of whitespacing in the .cl file, which makes it smaller.

All these .bins were built with the linked miner, from the 12th, so should be able to replicate; these weren't .bins yanked from aznboy84's miner.
One of the changes I saw in aznboy84's miner was that he is not using small footprint groestl at all
It isn't even an option in the darkcoin-mod.cl file
sr. member
Activity: 547
Merit: 250
[HELP AGAIN]
Mining X11 or x13? What do you guys think? which one is better for ROI?  Which version is better? sgminer v4.1 or v5.0?

lol
newbie
Activity: 61
Merit: 0
[HELP AGAIN]
Mining X11 or x13? What do you guys think? which one is better for ROI?  Which version is better? sgminer v4.1 or v5.0?
sr. member
Activity: 547
Merit: 250
So I disabled Unofficial Overclocking, and disabled ULPS in MSI AB; and rigs seem to be stable beyond 15mins.

I'm passing out for a bit but I won't be surprised if I wake up to some hung rigs.
sr. member
Activity: 294
Merit: 250
Nice, I don't have sick card, running for 10hours now.

I see u get about 200kh/s more with x13/x15, is it because of your higher memclock or because u change the cl for x13/x15? Otherwise can upload u your bin or cl?

I really wish I knew, I changed so much shit in the last 4 hours, I'm trying to find a stable rock before I go to sleep.

At 1050/1500 it ran but shit on itself when flipped algos; near the same for 1040/1400.  1040/1300 works on 2 rigs solid, but not 3rd.
1040/1300 and removing "disable ULPS" in MSI AB will not get you superhigh 5.9-6M hashrate, more like 5.6, but at least drivers hold.

It may have to do with MSI AB.

I don't think it's LUFFA...

I got the idea to sub the smaller groestl.cl in the folder, since all x[n] algos call for it, and it's the one that is most impacted by 14.6+
There's practically no change, except for lack of whitespacing in the .cl file, which makes it smaller.

All these .bins were built with the linked miner, from the 12th, so should be able to replicate; these weren't .bins yanked from aznboy84's miner.

Thanks, gonna test the linked sgminer and see what hashrates i get.
sr. member
Activity: 547
Merit: 250
Nice, I don't have sick card, running for 10hours now.

I see u get about 200kh/s more with x13/x15, is it because of your higher memclock or because u change the cl for x13/x15? Otherwise can upload u your bin or cl?

I really wish I knew, I changed so much shit in the last 4 hours, I'm trying to find a stable rock before I go to sleep.

At 1050/1500 it ran but shit on itself when flipped algos; near the same for 1040/1400.  1040/1300 works on 2 rigs solid, but not 3rd.
1040/1300 and removing "disable ULPS" in MSI AB will not get you superhigh 5.9-6M hashrate, more like 5.6, but at least drivers hold.

It may have to do with MSI AB.

I don't think it's LUFFA...

I got the idea to sub the smaller groestl.cl in the folder, since all x[n] algos call for it, and it's the one that is most impacted by 14.6+
There's practically no change, except for lack of whitespacing in the .cl file, which makes it smaller.

All these .bins were built with the linked miner, from the 12th, so should be able to replicate; these weren't .bins yanked from aznboy84's miner.
sr. member
Activity: 294
Merit: 250
Nice, I don't have sick card, running for 10hours now.

I see u get about 200kh/s more with x13/x15, is it because of your higher memclock or because u change the cl for x13/x15? Otherwise can upload u your bin or cl?
member
Activity: 70
Merit: 10
can this application also control the voltage ?!
member
Activity: 70
Merit: 10
whats wrong with this config ? sgminer keeps saying there is some error and the config file can't be used ...

Code:
"thread-concurrency" : "12800",

You can't end your last line before curly brackets with a hanging comma.

Go here and push your configs through please http://jsonlint.com/

Use the tools available from the previous 50 pages of people experiencing your similar problems...

....................................

thank you it works now Smiley
member
Activity: 70
Merit: 10
whats wrong with this config ? sgminer keeps saying there is some error and the config file can't be used ...

{
"pools" : [
     {
          "name" : "Scrypt",
          "url" : "stratum+tcp://stratum.nicehash.com:4333",
          "user" : "1yCntQL6PWhNzZGGbNwSFBy2YNotyma8T",
          "pass" : "x",
          "nfactor" : "10",
          "algorithm" : "zuikkis"
          "gpu-engine" : "850",
          "gpu-memclock" : "1250",
          "thread-concurrency" : "12800",
     },
     {
          "name" : "Scrypt-N",
          "url" : "stratum+tcp://stratum.nicehash.com:4335",
          "user" : "1yCntQL6PWhNzZGGbNwSFBy2YNotyma8T",
          "pass" : "x",
          "nfactor" : "11",
          "algorithm" : "zuikkis"
          "gpu-engine" : "850"
          "gpu-memclock" : "1250",
          "thread-concurrency" : "12800",
     },
     {
          "name" : "X11",
          "url" : "stratum+tcp://stratum.nicehash.com:4336",
          "user" : "1yCntQL6PWhNzZGGbNwSFBy2YNotyma8T",
          "pass" : "x",
          "nfactor" : "10",
          "algorithm" : "darkcoin-mod"
     },
     {
          "name" : "X13",
          "url" : "stratum+tcp://stratum.nicehash.com:4337",
          "user" : "1yCntQL6PWhNzZGGbNwSFBy2YNotyma8T",
          "pass" : "x",
          "nfactor" : "10",
          "algorithm" : "marucoin-mod"
     },
     {
          "name" : "Keccak",
          "url" : "stratum+tcp://stratum.nicehash.com:4338",
          "user" : "1yCntQL6PWhNzZGGbNwSFBy2YNotyma8T",
          "pass" : "x",
          "nfactor" : "10",
          "algorithm" : "maxcoin"
     },
     {
          "name" : "X15",
          "url" : "stratum+tcp://stratum.nicehash.com:4339",
          "user" : "1yCntQL6PWhNzZGGbNwSFBy2YNotyma8T",
          "pass" : "x",
          "nfactor" : "10",
          "algorithm" : "bitblock"
     },
     {
          "name" : "NIST5",
          "url" : "stratum+tcp://stratum.nicehash.com:4340",
          "user" : "1yCntQL6PWhNzZGGbNwSFBy2YNotyma8T",
          "pass" : "x",
          "nfactor" : "10",
          "algorithm" : "talkcoin-mod"
     }

"api-allow" : "W:127.0.0.1",
"api-listen" : true,
"api-port" : "4028",
"expiry" : "1",
"failover-only" : true,
"hotplug" : "5",
"log" : "5",
"queue" : "0",
"scan-time" : "1",
"shares" : "0",
"auto-fan" : true,
"intensity" : "19",
"gpu-engine" : "1000",
"gpu-memclock" : "1300",
"gpu-threads" : "4",
"gpu-dyninterval" : "7",
"gpu-fan" : "65",
"no-restart" : true,
"temp-target" : "80",
"temp-overheat" : "85",
"temp-cutoff" : "90",
"temp-hysteresis" : "3",
"worksize" : "256",
"thread-concurrency" : "8192",
"log-file" : "output.log",
"no-client-reconnect" : true,
"show-coindiff" : true,
"failover-switch-delay" : "30",
"hamsi-expand-big" : "1",
"hamsi-short" : true,
"extranonce-subscription" : true
}
Jump to: