[ANN] sgminer v5 - optimized X11/X13/NeoScrypt/Lyra2RE/etc. kernel-switch miner

[Ghost__]

Some help here would be greatly appreciated!

Finally got the multi-algo switching working right after much hair pulling, once I realized that a new CGWatcher version was out (auto update didn't pick it up).

However, when sgminer runs with the multi-algo config, after a few minutes, the miner dies saying that GPU0's status is UNKNOWN.  Using a config for a specific algo pool doesn't have this problem.

Config:

{
"pools" : [
    {    "name" : "NiceHash_Scrypt",
        "url" : "stratum+tcp://stratum.nicehash.com:4333",
        "user" : "1Jp4cZcpCjQrqkAaPisktfVgU1uHV7uVQc",
        "pass" : "f0=2.4;f2=1.1;f3=10.5;f4=7.5;f5=1200;c0=2.4;c2=2.4;c3=1.4;c4=1.4;c5=1.7",
        "pool-algorithm" : "zuikkis",
        "pool-nfactor" : "10",
        "pool-xintensity" : "400",
        "pool-gpu-engine" : "1000-1000",
        "pool-gpu-memclock" : "1300-1300",
        "pool-gpu-threads" : "1",
        "pool-thread-concurrency" : "25601"
    },
    {    "name" : "NiceHash_Scrypt-N",
        "url" : "stratum+tcp://stratum.nicehash.com:4335",
        "user" : "1Jp4cZcpCjQrqkAaPisktfVgU1uHV7uVQc",
        "pass" : "f0=2.4;f2=1.1;f3=10.5;f4=7.5;f5=1200;c0=2.4;c2=2.4;c3=1.4;c4=1.4;c5=1.7",
        "pool-algorithm" : "zuikkis",
        "pool-nfactor" : "11",
        "pool-xintensity" : "400",
        "pool-gpu-engine" : "1000-1000",
        "pool-gpu-memclock" : "1300-1300",
        "pool-gpu-threads" : "1",
        "pool-thread-concurrency" : "20481"
    },
    {    "name" : "NiceHash_x11",
        "url" : "stratum+tcp://stratum.nicehash.com:4336",
        "user" : "1Jp4cZcpCjQrqkAaPisktfVgU1uHV7uVQc",
        "pass" : "f0=2.4;f2=1.1;f3=10.5;f4=7.5;f5=1200;c0=2.4;c2=2.4;c3=1.4;c4=1.4;c5=1.7",
        "pool-algorithm" : "darkcoin-mod",
        "pool-nfactor" : "10",
        "pool-xintensity" : "400",
        "pool-gpu-engine" : "1000-1000",
        "pool-gpu-memclock" : "1300-1300",
        "pool-gpu-threads" : "4",
        "pool-thread-concurrency" : "25601"
    },
    {    "name" : "NiceHash_x13",
        "url" : "stratum+tcp://stratum.nicehash.com:4337",
        "user" : "1Jp4cZcpCjQrqkAaPisktfVgU1uHV7uVQc",
        "pass" : "f0=2.4;f2=1.1;f3=10.5;f4=7.5;f5=1200;c0=2.4;c2=2.4;c3=1.4;c4=1.4;c5=1.7",
        "pool-algorithm" : "marucoin-mod",
        "pool-nfactor" : "10",
        "pool-xintensity" : "400",
        "pool-gpu-engine" : "1000-1000",
        "pool-gpu-memclock" : "1300-1300",
        "pool-gpu-threads" : "4",
        "pool-thread-concurrency" : "25601"
    },
    {    "name" : "NiceHash_Keccak",
        "url" : "stratum+tcp://stratum.nicehash.com:4338",
        "user" : "1Jp4cZcpCjQrqkAaPisktfVgU1uHV7uVQc",
        "pass" : "f0=2.4;f2=1.1;f3=10.5;f4=7.5;f5=1200;c0=2.4;c2=2.4;c3=1.4;c4=1.4;c5=1.7",
        "pool-algorithm" : "maxcoin",
        "pool-nfactor" : "10",
        "pool-xintensity" : "300",
        "pool-gpu-engine" : "1000-1000",
        "pool-gpu-memclock" : "1300-1300",
        "pool-gpu-threads" : "1",
        "pool-thread-concurrency" : "25601"
    }
],

"no-submit-stale" : true,
"failover-only" : true,
"failover-switch-delay" : "30",
"no-pool-disable" : true,

"api-allow" : "W:127.0.0.1",
"api-description" : "m1-multi",
"api-listen" : true,
"api-port" : "4096",

"remove-disabled" : true,

"temp-cutoff" : "95",
"temp-overheat" : "87",
"temp-target" : "80",
"gpu-fan" : "50-100",
"auto-fan" : true,

"lookup-gap" : "2",
"worksize" : "128",
"shaders" : "2560",
"queue" : "1",
"expiry" : "1",
"scan-time" : "1",
"timeout" : "60",
"log" : "5",
"temp-hysteresis" : "3",

"kernel-path" : "/usr/local/bin"
}

Any help greatly appreciated!
Posted from Bitcointa.lk - #fy7HXpNBEQoRJU4r

Try setting the same "pool-gpu-threads" for all pools or remove the "pool-gpu-threads" and set it in the global section..!

Also try to use intensity instead of xintensity

[nicehashdev]

I suggest one more extra feature to be added, because current model can cause many rapid switches and as it appears sgminer needs some time to reach full speed when doing switch. We only drop connections every 15 minutes on NiceHash, but due to priority list in sgminer, sgminer will swap to higher priority pool as soon as that one is "stable" for 30 seconds? I suggest to make this value configurable in pool section. Use high values for multialgo pools and default (30) for backup pools and it should work fine (with no rapid switches). This extra feature is only 5 minute of work, so shouldn't be a big deal.

[platinum4]

I suggest one more extra feature to be added, because current model can cause many rapid switches and as it appears sgminer needs some time to reach full speed when doing switch. We only drop connections every 15 minutes on NiceHash, but due to priority list in sgminer, sgminer will swap to higher priority pool as soon as that one is "stable" for 30 seconds? I suggest to make this value configurable in pool section. Use high values for multialgo pools and default (30) for backup pools and it should work fine (with no rapid switches). This extra feature is only 5 minute of work, so shouldn't be a big deal.

I've extended failover-switch-delay to 300s right now.  I will report back if this mitigates SICK->DEAD.  Somewhere in the work being served, a thread goes lazy and always shits on the last GPU of a rig.

As far as extending SICK timer, adding in a GPU idle patch for when all pools are down and no work is available, and pthread_testcancel() all still result in rig crashing occasionally.  Two others are rock solid and would have 3 days up time if the city hadn't cut the power for a sec to work on the traffic lights I guess.

[nicehashdev]

Also it should be considered that detection of dead pool should work flawlessly. Because now, rig is disconnected upon auth (we don't get f and c parameters sooner than with password, so we can't know if rig should be disconnected or not). And yes, there were issues (idlebug) and these issues were solved, but solution might not be perfect.

[platinum4]

Also it should be considered that detection of dead pool should work flawlessly. Because now, rig is disconnected upon auth (we don't get f and c parameters sooner than with password, so we can't know if rig should be disconnected or not). And yes, there were issues (idlebug) and these issues were solved, but solution might not be perfect.

Code:

[07:23:22] Accepted Coin 836 Diff 0.103/0.040 GPU 0 at nh x11 multi 
[07:23:40] Accepted Coin 4368 Diff 0.044/0.040 GPU 1 at nh x11 multi 
[07:23:55] Accepted Coin 4368 Diff 0.207/0.040 GPU 0 at nh x11 multi 
[07:24:00] Stratum connection to nh x11 multi interrupted
[07:24:01] nh x11 multi not responding!
[07:24:01] Switching to nh keccak multi
[07:24:02] nh keccak multi not responding!
[07:24:02] Switching to tmb x13 multiport
[07:24:03] tmb x13 multiport not responding!
[07:24:03] Switching to tmb x13 multi east2
[07:24:03] tmb x13 multi east2 not responding!
[07:24:03] Switching to tmb x13 multi west
[07:24:05] tmb x13 multi west not responding!
[07:24:05] Switching to tmb x13 multi eu2
[07:24:06] tmb x13 multi eu2 not responding!
[07:24:06] Switching to tmb x11 multiport
[07:24:10] Waiting for work to be available from pools.
[07:24:10] Setting GPUs to idle performance.                <--- successful implementation of if have_ADL set to idle patch!!
[07:24:15] Work available from pools, resuming.
[07:24:16] Accepted Coin 836 Diff 0.008/0.005 GPU 0 at tmb x11 multiport 
[07:24:18] Accepted Coin 836 Diff 0.009/0.005 GPU 0 at tmb x11 multiport 
[07:24:20] tmb x11 multiport stale share detected, submitting (user)

Changing the failover-switch-delay parameter in the config file obviously won't fix the stratum drop.  Is there a softer way to do this?

Look at the timestamps... you're actually at half of 30 seconds, and closer to 15 seconds.  Is there another way to kill your stratum softer?

Here's how harshly it flips back when it's alive...

Code:

[07:33:35] Accepted Coin 4188 Diff 0.021/0.017 GPU 1 at tmb x11 multi 
[07:33:41] Stratum connection to tmb x11 multi interrupted
[07:33:42] tmb x11 multi not responding!
[07:33:42] Switching to nh x11 multi
[07:33:48] Stratum connection to nh x11 multi interrupted
[07:33:49] nh x11 multi difficulty changed to 0.040
[07:33:58] Accepted Coin 730 Diff 0.097/0.040 GPU 1 at nh x11 multi 

8 seconds between a disconnect from tmb and switch back to nh.  1/4 as long as 30s.

[nicehashdev]

NiceHash has all 4xxx ports alive - always, but all except one will drop connection as bad auth. As long as the switching on sgminer isn't performed too often  it should work fine.

[platinum4]

NiceHash has all 4xxx ports alive - always, but all except one will drop connection as bad auth. As long as the switching on sgminer isn't performed too often  it should work fine.

That's why I posted the logs.  It's obvious the switching in sgminer occurs on the scales of 8, 15, and possibly 30 seconds.  You've just been saying it should be longer...

Ok ok I see, you're proposing a change... post a github issue?

Code:

[09:02:55] Stratum connection to nh x11 multi interrupted
[09:02:56] nh x11 multi not responding!
[09:02:56] Switching to nh keccak multi
[09:02:56] nh keccak multi difficulty changed to 512
[09:03:05] Initialising kernel maxcoin.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[09:03:05] Initialising kernel maxcoin.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[09:03:18] Accepted Coin 16114 Diff 2.914/512 GPU 0 at nh keccak multi 
[09:03:19] Accepted Coin 16114 Diff 3.370/512 GPU 0 at nh keccak multi 
[09:03:34] Accepted Coin 16114 Diff 12/512 GPU 1 at nh keccak multi 
[09:03:34] Accepted Coin 16114 Diff 4.309/512 GPU 0 at nh keccak multi 
[09:03:50] Accepted Coin 16114 Diff 3.061/512 GPU 0 at nh keccak multi 
[09:03:54] Accepted Coin 15797 Diff 6.801/512 GPU 0 at nh keccak multi 
[09:03:54] nh keccak multi difficulty changed to 1024
[09:03:56] Accepted Coin 15797 Diff 6.801/1.02K GPU 0 at nh keccak multi 
[09:03:58] nh x11 multi alive, testing stability
[09:04:11] Accepted Coin 15797 Diff 4.549/1.02K GPU 1 at nh keccak multi 
[09:04:18] nh x11 multi stable for 30 seconds
[09:04:18] Switching to nh x11 multi
[09:04:19] Initialising kernel darkcoin-mod.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[09:04:19] Initialising kernel darkcoin-mod.cl with bitalign, unpatched BFI, nfactor 10, n 1024

Is this what you're referring to, with the 30 seconds?

EDIT:  Here is an example with failover-switch-delay : 90, notice how in 40 seconds, the nh x11 stratum drops, we wouldn't see this with the 30 second setting.

Code:

[09:12:45] Accepted Coin 15818 Diff 4.802/1.02K GPU 1 at nh keccak multi 
[09:13:04] Accepted Coin 15818 Diff 4.104/1.02K GPU 1 at nh keccak multi 
[09:13:07] nh x11 multi alive, testing stability
[09:13:10] Accepted Coin 15818 Diff 159/1.02K GPU 0 at nh keccak multi 
[09:13:19] Accepted Coin 15840 Diff 23/1.02K GPU 1 at nh keccak multi 
[09:13:27] Accepted Coin 15840 Diff 7.130/1.02K GPU 0 at nh keccak multi 
[09:13:50] Stratum connection to nh x11 multi interrupted
[09:13:57] Accepted Coin 15840 Diff 457/1.02K GPU 1 at nh keccak multi 
[09:14:02] Accepted Coin 15809 Diff 13/1.02K GPU 0 at nh keccak multi 
[09:14:05] Accepted Coin 15809 Diff 13/1.02K GPU 0 at nh keccak multi 
[09:14:06] Accepted Coin 15809 Diff 416/1.02K GPU 1 at nh keccak multi 
[09:14:34] Accepted Coin 15804 Diff 8.340/1.02K GPU 1 at nh keccak multi 
[09:14:43] Stratum connection to nh keccak multi interrupted
[09:14:44] nh keccak multi not responding!
[09:14:44] Switching to tmb x13 multiport
[09:14:44] tmb x13 multiport difficulty changed to 0.005
[09:14:53] Initialising kernel marucoin-mod.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[09:14:53] Initialising kernel marucoin-mod.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[09:14:54] nh x11 multi alive, testing stability
[09:15:09] Accepted Coin 80 Diff 0.018/0.005 GPU 1 at tmb x13 multiport 
[09:15:14] Accepted Coin 80 Diff 0.006/0.005 GPU 1 at tmb x13 multiport 
[09:15:16] Accepted Coin 80 Diff 0.006/0.005 GPU 0 at tmb x13 multiport 
[09:15:17] Accepted Coin 80 Diff 0.010/0.005 GPU 1 at tmb x13 multiport 
[09:15:20] Accepted Coin 80 Diff 0.015/0.005 GPU 1 at tmb x13 multiport 
[09:15:20] Accepted Coin 80 Diff 0.007/0.005 GPU 0 at tmb x13 multiport 
[09:15:22] Accepted Coin 80 Diff 0.019/0.005 GPU 0 at tmb x13 multiport 
[09:15:26] Accepted Coin 80 Diff 0.009/0.005 GPU 0 at tmb x13 multiport 
[09:15:33] Accepted Coin 80 Diff 0.006/0.005 GPU 0 at tmb x13 multiport 
[09:15:36] Accepted Coin 80 Diff 0.008/0.005 GPU 1 at tmb x13 multiport 
[09:15:37] Accepted Coin 80 Diff 0.015/0.005 GPU 1 at tmb x13 multiport 
[09:15:38] Accepted Coin 80 Diff 0.019/0.005 GPU 0 at tmb x13 multiport 
[09:15:38] Accepted Coin 80 Diff 0.006/0.005 GPU 1 at tmb x13 multiport 
[09:15:42] Accepted Coin 80 Diff 0.021/0.005 GPU 0 at tmb x13 multiport 
[09:15:43] Accepted Coin 80 Diff 0.022/0.005 GPU 0 at tmb x13 multiport 
[09:15:44] Accepted Coin 80 Diff 0.009/0.005 GPU 1 at tmb x13 multiport 
[09:15:44] Accepted Coin 80 Diff 0.006/0.005 GPU 1 at tmb x13 multiport 
[09:15:46] Accepted Coin 80 Diff 0.619/0.005 GPU 1 at tmb x13 multiport 
[09:15:49] Accepted Coin 80 Diff 0.007/0.005 GPU 0 at tmb x13 multiport 
[09:15:50] Accepted Coin 80 Diff 0.007/0.005 GPU 0 at tmb x13 multiport 
[09:15:51] tmb x13 multiport stale share detected, submitting (user)
[09:15:51] Accepted Coin 80 Diff 0.035/0.005 GPU 0 at tmb x13 multiport 
[09:15:55] Accepted Coin 81 Diff 0.011/0.005 GPU 1 at tmb x13 multiport 
[09:15:57] tmb x13 multiport difficulty changed to 0.018
[09:16:28] nh x11 multi stable for 90 seconds
[09:16:28] Switching to nh x11 multi
[09:16:28] Initialising kernel darkcoin-mod.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[09:16:28] Initialising kernel darkcoin-mod.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[09:16:33] Stratum connection to tmb x13 multiport interrupted
[09:17:09] Accepted Coin 606 Diff 0.058/0.050 GPU 1 at nh x11 multi 

See, I think it's actually something inside the miner that needs to be adjusted, because look at the harsh algo switch in around 20 seconds total elapsed time.

Code:

[09:14:43] Stratum connection to nh keccak multi interrupted
[09:14:44] nh keccak multi not responding!
[09:14:44] Switching to tmb x13 multiport
[09:14:44] tmb x13 multiport difficulty changed to 0.005
[09:14:53] Initialising kernel marucoin-mod.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[09:14:53] Initialising kernel marucoin-mod.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[09:14:54] nh x11 multi alive, testing stability

I can't tell if this commit is useful, or not, but I propose we use the idle state prior to initialzing a new algo kernel.

https://github.com/sgminer-dev/sgminer/commit/59bbe1b636cdb4a492e1ba15bc43ea9f20338ab1

[nem2k]

is it possible to integrate the lasybear x11 and x13 builds of sgminer:

https://bitcointalk.org/index.php?topic=623409.0

id love to jump on the multi algo mining train, but the traditional x11/13 miner builds have been much slower than the lasybear option

[platinum4]

is it possible to integrate the lasybear x11 and x13 builds of sgminer:

https://bitcointalk.org/index.php?topic=623409.0

id love to jump on the multi algo mining train, but the traditional x11/13 miner builds have been much slower than the lasybear option

Check your hamsi-expand-big : 1 (for 290/290X) [or 4 for 280/280X]

[platinum4]

Anybody know what's been going on with scrypt?  Been mining now for the last 12 hours plus on Nicehash.  Really odd comparing to all of last month...

[unitedminers]

(Help) SGMiner 5 - R9 290 - WU at 0.00 ??

I've switched from CGMiner with Scrypt (905KHs/ 820WU) to SGMiner 5 from Nicehash with X11 (3.2MHs/0.00WU) but WU is at 0.00. Any idea what's wrong with my SGMiner 5 settings?

My old CGMiner Scrypt settings:
./cgminer --scrypt -o stratum+tcp://stratum.scryptguild.com:3333 -u USER -p X --thread-concurrency 32765 -g 1 --worksize 512 --gpu-threads 1 -I 20

My new SGMiner 5 X11 settings:
./sgminer --algorithm darkcoin-mod -o stratum+tcp://eu.wafflepool.com:3331 -u USER -p X --thread-concurrency 32765 --gpu-threads 2 -w 512 -I 20

Thanks for every hint!

[rudarSRB]

Finally got the multi-algo switching working right after much hair pulling, once I realized that a new CGWatcher version was out (auto update didn't pick it up).

Link please.

[DarkAGeS]

Anybody know what's been going on with scrypt?  Been mining now for the last 12 hours plus on Nicehash.  Really odd comparing to all of last month...

it is Razorcoin

guys, does sgminer v5 work with new .bin files from 14.6 amd driver?
this miner https://bitcointalk.org/index.php?topic=623409.0 works perfectly, but sgminer v5 just crush after start

that is why more profitable to use x11-miner only, cause it has 4200kh on 280x.
sgminer 5 with old .bin hashrate 3200kh only

[coinmasters]

I will test on my r9 290,tnx

[oktay50000]

any version 5 with amd 14.6 fix???

[rudarSRB]

any version 5 with amd 14.6 fix???

+100

[ChilliWinter]

any version 5 with amd 14.6 fix???

+100

why not try .cl files from here : https://github.com/djm34/sph-sgminer_x11mod

I personaly switched this morning to the above miner, but will try cl files above with sgminer 5.

[btctradingonline]

any version 5 with amd 14.6 fix???

+100

why not try .cl files from here : https://github.com/djm34/sph-sgminer_x11mod

I personaly switched this morning to the above miner, but will try cl files above with sgminer 5.

+1

We're waiting for re_built sgminer ver 5 of multi-algo mining on Nicehash

[oktay50000]

any version 5 with amd 14.6 fix???

+100

why not try .cl files from here : https://github.com/djm34/sph-sgminer_x11mod

I personaly switched this morning to the above miner, but will try cl files above with sgminer 5.

im using this right now but it i need ver 5 with 14.6 for multi algo

[karimdr2]

How I can use blake kernel? I tried kernel and algorithm (blake, blake256) but sgminer does not recognize it