Bitcoin Forum
May 02, 2024, 10:24:22 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 [59] 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 ... 233 »
  Print  
Author Topic: [ANN] sgminer v5 - optimized X11/X13/NeoScrypt/Lyra2RE/etc. kernel-switch miner  (Read 877792 times)
badman74
Hero Member
*****
Offline Offline

Activity: 658
Merit: 500



View Profile
July 17, 2014, 12:01:13 PM
 #1161

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
1714645462
Hero Member
*
Offline Offline

Posts: 1714645462

View Profile Personal Message (Offline)

Ignore
1714645462
Reply with quote  #2

1714645462
Report to moderator
Transactions must be included in a block to be properly completed. When you send a transaction, it is broadcast to miners. Miners can then optionally include it in their next blocks. Miners will be more inclined to include your transaction if it has a higher transaction fee.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714645462
Hero Member
*
Offline Offline

Posts: 1714645462

View Profile Personal Message (Offline)

Ignore
1714645462
Reply with quote  #2

1714645462
Report to moderator
1714645462
Hero Member
*
Offline Offline

Posts: 1714645462

View Profile Personal Message (Offline)

Ignore
1714645462
Reply with quote  #2

1714645462
Report to moderator
1714645462
Hero Member
*
Offline Offline

Posts: 1714645462

View Profile Personal Message (Offline)

Ignore
1714645462
Reply with quote  #2

1714645462
Report to moderator
Trillium
Hero Member
*****
Offline Offline

Activity: 546
Merit: 500



View Profile
July 17, 2014, 12:24:55 PM
 #1162

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.

BTC:1AaaAAAAaAAE2L1PXM1x9VDNqvcrfa9He6
poiuty
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
July 17, 2014, 01:23:34 PM
 #1163

Anybody working on p2pool?
If so, what version?
mannyg
Full Member
***
Offline Offline

Activity: 142
Merit: 101


View Profile
July 17, 2014, 01:54:44 PM
 #1164

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
badman74
Hero Member
*****
Offline Offline

Activity: 658
Merit: 500



View Profile
July 17, 2014, 03:57:17 PM
 #1165

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
bullus
Sr. Member
****
Offline Offline

Activity: 294
Merit: 250


View Profile
July 17, 2014, 08:36:53 PM
 #1166

Working config for scrypt/nscrypt/x11/x13/x14/x15/keccak/nist5/qubit algos on 3x 290X (shaders 2816) rig on CGWatcher 1.4.1, W7x64 CCC 14.7RC
updated with badman74's advice on temperature targets; overclocks with lower intensities to avoid driver failures; removed redundant settings, globally specified "gpu-threads" : "2", and removed redundant gpu-threads settings on relevant profiles; disabled ULPS in MSI AB; substituted 65KB groestl.cl in place of 67KB groestl.cl; #define SPH_LUFFA_PARALLEL 1 in darkcoin-mod.cl, marucoin-mod.cl, x14.cl, bitblock.cl; #include "aes_helper.cl" in 39KB darkcoin-mod.cl; dropped worksize to 64 like bullus; recalibrated speedfactors for nicehash password field.

https://www.nicehash.com/software/nightly/sgminer-5.0-daily-20140712-15-win32.zip

Hashrates:

x11: 5.74M
x13: 4.5M
x14: 4.2M
x15: 4M
nist5: 17.7M
keccak: 470M
scrypt: disabled
nscrypt: disabled
qubit: disabled
fresh: disabled


sgminer.conf
Code:
{
"pools" : [
{
"name" : "br x15 platinum4.2",
"url" : "stratum+tcp://r6214.g51.rigs.eu.betarigs.com:9045",
"user" : "platinumstephen-6214",
"pass" : "x",
"pool-priority" : "0",
"profile" : "x15"
},
{
"name" : "hashbusters x11 test",
"url" : "stratum+tcp://192.99.148.34:5555",
"user" : "19VAeHKFfo91wxPhXQAEvHbkV4B2t5yRgq",
"pass" : "x",
"pool-priority" : "1",
"profile" : "x11",
"state" : "disabled"
},
{
"name" : "mrr nist5 platinum4.2",
"url" : "http://us-central01.miningrigrentals.com:3333",
"user" : "platinumstephen.5405",
"pass" : "x",
"pool-priority" : "2",
"profile" : "nist5"
},
{
"name" : "mrr nist5 platinum4.2 (2)",
"url" : "http://us-east01.miningrigrentals.com:3333",
"user" : "platinumstephen.5405",
"pass" : "x",
"pool-priority" : "3",
"profile" : "nist5"
},
{
"name" : "mrr nist5 platinum4.2 (3)",
"url" : "http://us-west01.miningrigrentals.com:3333",
"user" : "platinumstephen.5405",
"pass" : "x",
"pool-priority" : "4",
"profile" : "nist5"
},
{
"name" : "mrr nist5 platinum4.2 (4)",
"url" : "http://eu-01.miningrigrentals.com:3333",
"user" : "platinumstephen.5405",
"pass" : "x",
"pool-priority" : "5",
"profile" : "nist5"
},
{
"name" : "mrr nist5 platinum4.2 (5)",
"url" : "http://ap-01.miningrigrentals.com:3333",
"user" : "platinumstephen.5405",
"pass" : "x",
"pool-priority" : "6",
"profile" : "nist5"
},
{
"name" : "nh x15 multi",
"url" : "stratum+tcp://stratum.nicehash.com:4339",
"user" : "19VAeHKFfo91wxPhXQAEvHbkV4B2t5yRgq",
"pass" : "d=0.100;f0=2.95;f2=1.45;f3=18;f4=13.2;f5=1440;f6=12;f7=52.8;c0=2.9;c2=2.9;c3=1.8;c4=1.8;c5=2.4;c6=1.8;c7=1.6",
"pool-priority" : "7",
"profile" : "x15"
},
{
"name" : "nh x13 multi",
"url" : "stratum+tcp://stratum.nicehash.com:4337",
"user" : "19VAeHKFfo91wxPhXQAEvHbkV4B2t5yRgq",
"pass" : "d=0.100;f0=2.95;f2=1.45;f3=18;f4=13.2;f5=1440;f6=12;f7=52.8;c0=2.9;c2=2.9;c3=1.8;c4=1.8;c5=2.4;c6=1.8;c7=1.6",
"pool-priority" : "8",
"profile" : "x13"
},
{
"name" : "nh x11 multi",
"url" : "stratum+tcp://stratum.nicehash.com:4336",
"user" : "19VAeHKFfo91wxPhXQAEvHbkV4B2t5yRgq",
"pass" : "d=0.100;f0=2.95;f2=1.45;f3=18;f4=13.2;f5=1440;f6=12;f7=52.8;c0=2.9;c2=2.9;c3=1.8;c4=1.8;c5=2.4;c6=1.8;c7=1.6",
"pool-priority" : "9",
"profile" : "x11"
},
{
"name" : "nh nist5 multi",
"url" : "stratum+tcp://stratum.nicehash.com:4340",
"user" : "19VAeHKFfo91wxPhXQAEvHbkV4B2t5yRgq",
"pass" : "d=0.100;f0=2.95;f2=1.45;f3=18;f4=13.2;f5=1440;f6=12;f7=52.8;c0=2.9;c2=2.9;c3=1.8;c4=1.8;c5=2.4;c6=1.8;c7=1.6",
"pool-priority" : "10",
"profile" : "nist5"
},
{
"name" : "nh keccak multi",
"url" : "stratum+tcp://stratum.nicehash.com:4338",
"user" : "19VAeHKFfo91wxPhXQAEvHbkV4B2t5yRgq",
"pass" : "d=1024;f0=2.95;f2=1.45;f3=18;f4=13.2;f5=1440;f6=12;f7=52.8;c0=2.9;c2=2.9;c3=1.8;c4=1.8;c5=2.4;c6=1.8;c7=1.6",
"pool-priority" : "11",
"profile" : "keccak"
},
{
"name" : "nh scrypt multi",
"url" : "stratum+tcp://stratum.nicehash.com:4333",
"user" : "19VAeHKFfo91wxPhXQAEvHbkV4B2t5yRgq",
"pass" : "d=1024;f0=2.95;f2=1.45;f3=18;f4=13.2;f5=1440;f6=12;f7=52.8;c0=2.9;c2=2.9;c3=1.8;c4=1.8;c5=2.4;c6=1.8;c7=1.6",
"pool-priority" : "12",
"profile" : "scrypt",
"state" : "disabled"
},
{
"name" : "nh nscrypt multi",
"url" : "stratum+tcp://stratum.nicehash.com:4335",
"user" : "19VAeHKFfo91wxPhXQAEvHbkV4B2t5yRgq",
"pass" : "d=512;f0=2.95;f2=1.45;f3=18;f4=13.2;f5=1440;f6=12;f7=52.8;c0=2.9;c2=2.9;c3=1.8;c4=1.8;c5=2.4;c6=1.8;c7=1.6",
"pool-priority" : "13",
"profile" : "scrypt",
"state" : "disabled"
},
{
"name" : "nh x15 multi failover",
"url" : "stratum+tcp://stratum.nicehash.com:3339",
"user" : "19VAeHKFfo91wxPhXQAEvHbkV4B2t5yRgq",
"pass" : "x",
"pool-priority" : "14",
"profile" : "x15"
},
{
"name" : "mrr x15 platinum4.2",
"url" : "http://us-central01.miningrigrentals.com:3333",
"user" : "platinumstephen.3982",
"pass" : "x",
"pool-priority" : "15",
"profile" : "x15"
},
{
"name" : "mrr x15 platinum4.2 (2)",
"url" : "http://us-east01.miningrigrentals.com:3333",
"user" : "platinumstephen.3982",
"pass" : "x",
"pool-priority" : "16",
"profile" : "x15"
},
{
"name" : "mrr x15 platinum4.2 (3)",
"url" : "http://us-west01.miningrigrentals.com:3333",
"user" : "platinumstephen.3982",
"pass" : "x",
"pool-priority" : "17",
"profile" : "x15"
},
{
"name" : "mrr x15 platinum4.2 (4)",
"url" : "http://eu-01.miningrigrentals.com:3333",
"user" : "platinumstephen.3982",
"pass" : "x",
"pool-priority" : "18",
"profile" : "x15"
},
{
"name" : "mrr x15 platinum4.2 (5)",
"url" : "http://ap-01.miningrigrentals.com:3333",
"user" : "platinumstephen.3982",
"pass" : "x",
"pool-priority" : "19",
"profile" : "x15"
},
{
"name" : "mrr x13 platinum4.2",
"url" : "http://us-central01.miningrigrentals.com:3333",
"user" : "platinumstephen.1768",
"pass" : "x",
"pool-priority" : "20",
"profile" : "x13"
},
{
"name" : "mrr x13 platinum4.2 (2)",
"url" : "http://us-east01.miningrigrentals.com:3333",
"user" : "platinumstephen.1768",
"pass" : "x",
"pool-priority" : "21",
"profile" : "x13"
},
{
"name" : "mrr x13 platinum4.2 (3)",
"url" : "http://us-west01.miningrigrentals.com:3333",
"user" : "platinumstephen.1768",
"pass" : "x",
"pool-priority" : "22",
"profile" : "x13"
},
{
"name" : "mrr x13 platinum4.2 (4)",
"url" : "http://eu-01.miningrigrentals.com:3333",
"user" : "platinumstephen.1768",
"pass" : "x",
"pool-priority" : "23",
"profile" : "x13"
},
{
"name" : "mrr x13 platinum4.2 (5)",
"url" : "http://ap-01.miningrigrentals.com:3333",
"user" : "platinumstephen.1768",
"pass" : "x",
"pool-priority" : "24",
"profile" : "x13"
},
{
"name" : "mrr x11 platinum4.2",
"url" : "http://us-central01.miningrigrentals.com:3333",
"user" : "platinumstephen.4265",
"pass" : "x",
"pool-priority" : "25",
"profile" : "x11"
},
{
"name" : "mrr x11 platinum4.2 (2)",
"url" : "http://us-east01.miningrigrentals.com:3333",
"user" : "platinumstephen.4265",
"pass" : "x",
"pool-priority" : "26",
"profile" : "x11"
},
{
"name" : "mrr x11 platinum4.2 (3)",
"url" : "http://us-west01.miningrigrentals.com:3333",
"user" : "platinumstephen.4265",
"pass" : "x",
"pool-priority" : "27",
"profile" : "x11"
},
{
"name" : "mrr x11 platinum4.2 (4)",
"url" : "http://eu-01.miningrigrentals.com:3333",
"user" : "platinumstephen.4265",
"pass" : "x",
"pool-priority" : "28",
"profile" : "x11"
},
{
"name" : "mrr x11 platinum4.2 (5)",
"url" : "http://ap-01.miningrigrentals.com:3333",
"user" : "platinumstephen.4265",
"pass" : "x",
"pool-priority" : "29",
"profile" : "x11"
},
{
"name" : "hh x14",
"url" : "stratum+tcp://www.hashharder.com:9672",
"user" : "Xwxs3zrR8XEsFfmzQXHbioYBu7abg6dzqh",
"pass" : "x",
"pool-priority" : "30",
"profile" : "x14"
},
{
"name" : "hh qubit",
"url" : "stratum+tcp://www.hashharder.com:9674",
"user" : "DGsGKdzJYrtHKBT2gH7UKTwP9EAi56xEfD",
"pass" : "x",
"pool-priority" : "31",
"profile" : "qubit"
}
],
"api-allow" : "W:127.0.0.1",
"api-listen" : true,
"gpu-threads" : "2",
"temp-target" : "88",
"temp-overheat" : "92",
"temp-cutoff" : "96",
"include" : "profiles.conf"
}

profiles.conf
Code:
{
"profiles" : [
{
"name" : "x11",
"algorithm" : "darkcoin-mod",
"intensity" : "17",
"worksize": "64",
"gpu-engine": "1040",
"gpu-memclock": "1300",
"gpu-fan" : "80-100"
},
{
"name" : "x13",
"algorithm" : "marucoin-mod",
"intensity" : "17",
"worksize": "64",
"gpu-engine": "1040",
"gpu-memclock": "1300",
"gpu-fan" : "80-100"
},
{
"name" : "x14",
"algorithm" : "x14",
"intensity" : "17",
"worksize": "64",
"gpu-engine": "1040",
"gpu-memclock": "1300",
"gpu-fan" : "80-100"
},
{
"name" : "x15",
"algorithm" : "bitblock",
"intensity" : "17",
"worksize": "64",
"gpu-engine": "1040",
"gpu-memclock": "1300",
"gpu-fan" : "80-100"
},
{
"name" : "nist5",
"algorithm" : "talkcoin-mod",
"intensity" : "16",
"worksize": "64",
"gpu-engine": "1040",
"gpu-memclock": "1300",
"gpu-fan" : "80-100"
},
{
"name" : "qubit",
"algorithm" : "qubitcoin",
"intensity" : "21",
"worksize": "256",
"gpu-engine": "1040",
"gpu-memclock": "1300",
"gpu-fan" : "80-100"
},
{
"name" : "scrypt",
"xintensity" : "640",
"worksize" : "256",
"lookup-gap" : "2",
"vectors" : "1",
"gpu-threads": "1",
"algorithm" : "alexkarnew",
"nfactor" : "10",
"gpu-engine" : "1000",
"gpu-memclock" : "1250",
"gpu-fan" : "85-100",
"thread-concurrency" : "16384"
},
{
"name" : "nscrypt",
"xintensity" : "320",
"worksize" : "256",
"lookup-gap" : "2",
"vectors" : "1",
"gpu-threads": "1",
"algorithm" : "alexkarnew",
"nfactor" : "11",
"gpu-engine" : "1000",
"gpu-memclock" : "1250",
"gpu-fan" : "85-100",
"thread-concurrency" : "8192"
},
{
"name" : "keccak",
"intensity" : "13",
"worksize" : "256",
"lookup-gap" : "2",
"gpu-threads": "1",
"algorithm" : "maxcoin",
"gpu-engine" : "1020",
"gpu-memclock" : "1375",
"gpu-fan" : "85-100",
"thread-concurrency" : "32765"
}
],
"expiry" : "1",
"failover-only" : true,
"scan-time" : "1",
"auto-fan" : true,
"no-restart" : true,
"shaders" : "2816",
"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
}

This may throw some cards SICK very fast/frequently (don't be surprised if it's less than 30 minutes uptime)
Please report back with results, and CGWatcher should have your back on SICKs.  Already was too ambitious; had to drop to 1040/1300.

Hashrates with the link miner

x11   :5.5Mh/s --> using other bin 6.05Mh/s
x13   :4.4Mh/s
x15   :3.9Mh/s
nist5 :17.8Mh/s

profiles.conf
Code:
{
"profiles" : [
{
"name" : "x11",
"algorithm" : "darkcoin-mod",
"intensity" : "16",
"gpu-threads" : "2",
"worksize": "64"
},
{
"name" : "x13",
"algorithm" : "marucoin-mod",
"intensity" : "17",
"gpu-threads" : "2",
"worksize": "64"
},
{
"name" : "x15",
"algorithm" : "bitblock",
"intensity" : "17",
"gpu-threads" : "2",
"worksize": "64"
},
{
"name" : "nist5",
"algorithm" : "talkcoin-mod",
"intensity" : "16",
"gpu-threads" : "2",
"worksize": "64"
}
],
"default-profile": "x15",
"hamsi-expand-big" : "1",
"shaders" : "2816",
"gpu-fan" : "85-100",
"gpu-powertune" : "15",
"auto-fan" : true,
"auto-gpu" : true,
"failover-only" : true,
"expiry" : "1",
"gpu-dyninterval" : "7",
"hotplug" : "5",
"log" : "5",
"queue" : "0",
"scan-time" : "1",
"temp-hysteresis" : "2",
"shares" : "0",
"no-submit-stale" : true,
"no-restart" : true,
"failover-switch-delay" : "30",
"show-coindiff" : true,
"remove-disabled" : true,
"extranonce-subscription" : true
}

btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
platinum4
Sr. Member
****
Offline Offline

Activity: 547
Merit: 250



View Profile
July 18, 2014, 12:12:40 AM
 #1167

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?
badman74
Hero Member
*****
Offline Offline

Activity: 658
Merit: 500



View Profile
July 18, 2014, 02:18:34 AM
Last edit: July 18, 2014, 03:21:44 AM by badman74
 #1168

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
Undland
Legendary
*
Offline Offline

Activity: 1120
Merit: 1055



View Profile
July 18, 2014, 04:19:10 AM
 #1169

Every day my miner is turning off one or two times. Both Windows and Linux versions. Sometimes i losing profit for 6 hours, before i detect offline rigs. Sad
platinum4
Sr. Member
****
Offline Offline

Activity: 547
Merit: 250



View Profile
July 18, 2014, 05:43:48 AM
 #1170

Every day my miner is turning off one or two times. Both Windows and Linux versions. Sometimes i losing profit for 6 hours, before i detect offline rigs. Sad
Every day I'm hustlin' hustlin' every every day I'm hustlin'...
platinum4
Sr. Member
****
Offline Offline

Activity: 547
Merit: 250



View Profile
July 18, 2014, 06:05:06 AM
 #1171

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

Yeah I've topped out, with bullus's bins I can hit 5.88 stable on my clocks, without having to deal with hung rigs; applying every one of those hacks plus KECCAK UNROLL 1 in marucoin-mod, x14, & bitblock leaves me at near the same speeds I had posted with my configs, so I think once hamsi is added in, the hamsi-short and hamsi_helper take over in terms of performance.

Your groestl.cl changes were kind of cool to try, but the original 2 loops at the end of groestl.cl seem to work better as they are, instead of shortened.  I think the key here is to keep the .cl file as small and as short as possible; I wonder if editing out the copyright contents would make for a shorter file? Grin

Can those 2 last loops you altered be pragma unrolled?
platinum4
Sr. Member
****
Offline Offline

Activity: 547
Merit: 250



View Profile
July 18, 2014, 06:32:28 AM
 #1172

So I got bored, and I read through all of the comments on each .cl file that was part of x11/x13/x14/x15.

Here's what I found.

hamsi-expand-big '1' performs similar to hamsi-expand-big '8' with hamsi-short: true
keccak unroll 0 turns into keccak unroll 8 by default, so tried specifying keccak unroll 2 which is for smaller machines

And pretty much no change in hashrate, NO LOSS, but... no gain.

Intensity 17 seems to be the best setting, which is I:17 =  131072 threads

Later on I think I may experiment with xintensities that are between both 16 (drop in hash) and 17, and 17 and 18 (drop in hash)

For right now, no hung rigs on hamsi-expand-big '8', then again, no real difference noticed either.
poiuty
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
July 18, 2014, 06:32:48 AM
 #1173

badman74, thx!
Now my R9 290 non-x ~5600Kh/s

Quote
"kernel": "darkcoin-mod",
"xintensity" : "50",
"gpu-threads" : "2",
"lookup-gap" : "2",
"worksize" : "128",
"gpu-powertune" : "0",
"gpu-engine" : "1100",
"gpu-memclock" : "1500",
Eastwind
Hero Member
*****
Offline Offline

Activity: 896
Merit: 1000



View Profile
July 18, 2014, 08:03:08 AM
 #1174


Working config for scrypt/nscrypt/x11/x13/x14/x15/keccak/nist5/qubit algos on 3x 290X (shaders 2816) rig on CGWatcher 1.4.1, W7x64 CCC 14.7RC
updated with badman74's advice on temperature targets; overclocks with lower intensities to avoid driver failures; removed redundant settings, globally specified "gpu-threads" : "2", and removed redundant gpu-threads settings on relevant profiles; disabled ULPS in MSI AB; substituted 65KB groestl.cl in place of 67KB groestl.cl; #define SPH_LUFFA_PARALLEL 1 in darkcoin-mod.cl, marucoin-mod.cl, x14.cl, bitblock.cl; #include "aes_helper.cl" in 39KB darkcoin-mod.cl; dropped worksize to 64 like bullus; recalibrated speedfactors for nicehash password field.


Do you use the 65k or 67kb version?

Is it possible to upload the modified files?

phzi
Hero Member
*****
Offline Offline

Activity: 700
Merit: 500


View Profile
July 18, 2014, 09:07:38 AM
Last edit: July 18, 2014, 09:21:58 AM by phzi
 #1175

No idea what the heck I did...

I was pulling 4.5MH/s for X11 on each R9 290 before today (with fairly conservative clocks too).  Tried some of the cl modifications in this thread, deleted existing bins, and my hashrate dropped.  
Even cloned and compiled a fresh copy of sgminer.  Hashrate is maxing out at 3.11MH/s now no matter what I do.

It's a Gentoo Linux rig with 14.6 ati-drivers.

This profile was working great for me before (stable 4.5MH/s ... ran for days without issue)
Code:
 {
                "name" : "X11",
                "algorithm" : "darkcoin-mod",
                "xintensity" : "256",
                "gpu-threads" : "1",
                "gpu-powertune" : "1",
                "worksize": "128",
                "gpu-engine": "980-980",
                "gpu-memclock": "1300",
                "gpu-fan": "60"
        },

What the heck did I do, lol?
platinum4
Sr. Member
****
Offline Offline

Activity: 547
Merit: 250



View Profile
July 18, 2014, 09:25:31 AM
 #1176

No idea what the heck I did...

I was pulling 4.5MH/s for X11 on each R9 290 before today (with fairly conservative clocks too).  Tried some of the cl modifications in this thread, deleted existing bins, and my hashrate dropped.  
Even cloned and compiled a fresh copy of sgminer.  Hashrate is maxing out at 3.11MH/s now no matter what I do.

It's a Gentoo Linux rig with 14.6 ati-drivers.

This profile was working great for me before (stable 4.5MH/s ... ran for days without issue)
Code:
 {
                "name" : "X11",
                "algorithm" : "darkcoin-mod",
                "xintensity" : "256",
                "gpu-threads" : "1",
                "gpu-powertune" : "1",
                "worksize": "128",
                "gpu-engine": "980-980",
                "gpu-memclock": "1300",
                "gpu-fan": "60"
        },

What the heck did I do, lol?

gpu-threads:2
xinstensity:50

remove auto-gpu
set one frequency for gpu-engine

enable auto-fan
set fan range from 60-100
platinum4
Sr. Member
****
Offline Offline

Activity: 547
Merit: 250



View Profile
July 18, 2014, 09:26:32 AM
 #1177


Working config for scrypt/nscrypt/x11/x13/x14/x15/keccak/nist5/qubit algos on 3x 290X (shaders 2816) rig on CGWatcher 1.4.1, W7x64 CCC 14.7RC
updated with badman74's advice on temperature targets; overclocks with lower intensities to avoid driver failures; removed redundant settings, globally specified "gpu-threads" : "2", and removed redundant gpu-threads settings on relevant profiles; disabled ULPS in MSI AB; substituted 65KB groestl.cl in place of 67KB groestl.cl; #define SPH_LUFFA_PARALLEL 1 in darkcoin-mod.cl, marucoin-mod.cl, x14.cl, bitblock.cl; #include "aes_helper.cl" in 39KB darkcoin-mod.cl; dropped worksize to 64 like bullus; recalibrated speedfactors for nicehash password field.


Do you use the 65k or 67kb version?

Is it possible to upload the modified files?



http://pastebin.com/0aia0VXU

or

https://bitcointalk.org/index.php?topic=632503.msg7902608#msg7902608

badman has 2 loops changed at the end of his groestl.cl though
phzi
Hero Member
*****
Offline Offline

Activity: 700
Merit: 500


View Profile
July 18, 2014, 09:36:15 AM
 #1178

No idea what the heck I did...

I was pulling 4.5MH/s for X11 on each R9 290 before today (with fairly conservative clocks too).  Tried some of the cl modifications in this thread, deleted existing bins, and my hashrate dropped.  
Even cloned and compiled a fresh copy of sgminer.  Hashrate is maxing out at 3.11MH/s now no matter what I do.

It's a Gentoo Linux rig with 14.6 ati-drivers.

This profile was working great for me before (stable 4.5MH/s ... ran for days without issue)
Code:
 {
                "name" : "X11",
                "algorithm" : "darkcoin-mod",
                "xintensity" : "256",
                "gpu-threads" : "1",
                "gpu-powertune" : "1",
                "worksize": "128",
                "gpu-engine": "980-980",
                "gpu-memclock": "1300",
                "gpu-fan": "60"
        },

What the heck did I do, lol?

gpu-threads:2
xinstensity:50

remove auto-gpu
set one frequency for gpu-engine

enable auto-fan
set fan range from 60-100
Worse.  2.7MH/s max with those settings.  If I drop xI to 32 I can get 2.8MH/s.  And... one card just went SICK VERY fast.

Code:
        {
                "name" : "X11",
                "algorithm" : "darkcoin-mod",
                "xintensity" : "50",
                "gpu-threads" : "2",
                "gpu-powertune" : "10",
                "worksize": "128",
                "gpu-engine": "980",
                "gpu-memclock": "1300",
                "gpu-fan": "60-100",
                "auto-fan" : true,
                "auto-gpu" : false
        },

It shouldn't be a configuration issue... I had 4.5MH/s rock solid with the settings above up until I had to re-compile sgminer...

Tried a few different GCC versions even, same thing.

---

Edit: these cards simply do not like gpu-threads: 2.  It's ALWAYS worse performance for me.  Using the exact settings your suggest, but gpu-threads: 1 results in 2.95MH/s.

Auto-fan is also unneccesary for me, as the cards never go over 70.0C at 60% fan (so, auto-fan will never ramp up the fans anyway).
platinum4
Sr. Member
****
Offline Offline

Activity: 547
Merit: 250



View Profile
July 18, 2014, 09:48:28 AM
 #1179

idk man, if you had something working before, then try that again.

if you have it all fucked up, save your conf files, and blast it all, then recompile and try again.
phzi
Hero Member
*****
Offline Offline

Activity: 700
Merit: 500


View Profile
July 18, 2014, 09:51:42 AM
 #1180

idk man, if you had something working before, then try that again.

if you have it all fucked up, save your conf files, and blast it all, then recompile and try again.
Ya, this is what's messing with me...  I nuked sgminer, cloned from v5_0 git, re-compiled, and... 3.11MH/s.  Exact same config as was giving me 4.5MH/s.

Boggling my mind... nothing else has changed that I can think of.

I dropped 2 cl files in to test, started sgminer and got 3.11MH/s; and, each time I quit and launched sgminer after the hashrate dropped (as if there were memleaks or something).  Rebooting, re-compiling, hard reboot (shutdown, wait a while, start again)... still 3.11MH/s.

The only thing I can think is that my 4.5MH/s bin file was generated on a slightly older sgminer codebase (but I was running it in the latest sgminer compile).  Screw me for not copying the .bin before deleting it.
Pages: « 1 ... 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 [59] 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 ... 233 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!