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

[platinum4]

@aznboy84 is this 32 bit version should it make difference if I try to build 64 bit one.

Got a x64 version too but there's no point, no hashrate difference between x32 and x64
here goes the x64 build
https://mega.co.nz/#!EJVWEK6D!atU0PRIfcKpP9WowkgsJT0GDXctnQPo_CarfCaSWkJ8

[grippy54]

For 290X

Cool approach to your config.

[guzzzi]

Is there any BAMT Version out with the latest SGMiner V5? Would be nice to Download, still got Problems with 6 GPUs in my Rig and try to change the System to a USB-Linux and SGMiner V5.

[Trillium]

You just destroyed my brain trying to work out why it was only mining on one card.

It turns out that "devices" command line must now be specified in the pools section. Is there a list somewhere of command line options that you moved to the pools section of the config?
To those finding that marucoin-mod is slower than x13mod, try changing

"gpu-threads" : "1",     (set between 1 to 4)

and

"hamsi-expand-big" : "1",    (set to 1 or 4, check .bin file reflects this change)

Going from sph-sgminer to sgminer v5, I had to add "hamsi-expand-big" and change threads from 4 to 1. Now they hash at virtually the same. (Marucoin hashrate is truely terrible when threads is on 4).

[Kablam]

Is there any BAMT Version out with the latest SGMiner V5? Would be nice to Download, still got Problems with 6 GPUs in my Rig and try to change the System to a USB-Linux and SGMiner V5.

use pimp

dö the latest pimp on http://getpimp.org/ and us pimp update ti install the miner.

[badman74]

You just destroyed my brain trying to work out why it was only mining on one card.

It turns out that "devices" command line must now be specified in the pools section. Is there a list somewhere of command line options that you moved to the pools section of the config?
To those finding that marucoin-mod is slower than x13mod, try changing

"gpu-threads" : "1",     (set between 1 to 4)

and

"hamsi-expand-big" : "1",    (set to 1 or 4, check .bin file reflects this change)

Going from sph-sgminer to sgminer v5, I had to add "hamsi-expand-big" and change threads from 4 to 1. Now they hash at virtually the same. (Marucoin hashrate is truely terrible when threads is on 4).

Check doc/configuration.md

[guzzzi]

Is there any BAMT Version out with the latest SGMiner V5? Would be nice to Download, still got Problems with 6 GPUs in my Rig and try to change the System to a USB-Linux and SGMiner V5.

use pimp

dö the latest pimp on http://getpimp.org/ and us pimp update ti install the miner.

Many Thanks for the Hint, never heared of Pimp (maybe im not long enough in this Mining ). So after Update i can get this Multi-Algo-Switch SGMiner for NiceHash, right? Will try this soon.

[lucid_ity]

Am I the only one who sees the ridiculousness of these performance improvements with increased power usage?

Sure, the early adopters get an advantage over those who haven't used the new technology yet.   In the long run, however, everyone will be using them.   This means difficulty goes up, and we're back where we were before, except now with higher energy costs and hotter graphics cards.  Less profits for all (except the energy companies)! Hooray!

[platinum4]

Am I the only one who sees the ridiculousness of these performance improvements with increased power usage?

Sure, the early adopters get an advantage over those who haven't used the new technology yet.   In the long run, however, everyone will be using them.   This means difficulty goes up, and we're back where we were before, except now with higher energy costs and hotter graphics cards.  Less profits for all (except the energy companies)! Hooray!

Still better than no profits, which is current for mining BTC/LTC/FTC/Quark, etc.

[platinum4]

Don't have any HD58XX for testing but i could use some info ... does your HD58XX works with the marucoin-modold or x13modold ?

With x13modold

Done ... let's give it a try
https://mega.co.nz/#!sZcGySSQ!GoeiVnJ1Kc2UTt40AIT_gCenDX8xw1L6-Vi2ZHs1gZA

aznboy84, can you pull request with ystarnaud over at https://github.com/sgminer-dev/sgminer/tree/v5_0-new-algo ?

Can't ... just signed up github today ... but i guess it's private

How do we get this guy's pull request to go through?

[platinum4]

You just destroyed my brain trying to work out why it was only mining on one card.

It turns out that "devices" command line must now be specified in the pools section. Is there a list somewhere of command line options that you moved to the pools section of the config?
To those finding that marucoin-mod is slower than x13mod, try changing

"gpu-threads" : "1",     (set between 1 to 4)

and

"hamsi-expand-big" : "1",    (set to 1 or 4, check .bin file reflects this change)

Going from sph-sgminer to sgminer v5, I had to add "hamsi-expand-big" and change threads from 4 to 1. Now they hash at virtually the same. (Marucoin hashrate is truely terrible when threads is on 4).

Delete bins?  What CCC version you on 13 or 14?

[lucid_ity]

Still better than no profits, which is current for mining BTC/LTC/FTC/Quark, etc.

For sure.  But with the increased energy costs due to "progress" we're that much closer to no profits.  Oh well, can't fight it I guess

[mannyg]

Man, where do i begin.  I've tweaked and changed so many things just to see how stable I can get things, here is where I am at:

4 x 280x - MSI Gaming 4G
This thing runs solid.  X11 & X13 switching works great. Scrypt to Scrypt-N works great. Keccak works great but rejects are a little high.. ~10%-ish.
I dont have ALL of the algos on one conf file and I am stopping and starting the mining manually as I see profitability changing... but I do miss changes too.

X11 - darkcoin-mod  3.25MH/s sustained solid
X13 - marucoin-mod 2.55MH/s sustained solid

intensity - 17
worksize - 256
gpu-engine - 1125
gpu-memclock - 1500
gpu-powertune - -20
gpu-threads - 2
hamsi-expand-big - 4

I'm not defining a thread concurrency for X11/X13.  Is it even necessary? I do define shaders - 2048 though.

Scrypt - zukkis - 730KH/s sustained solid
Scrypt-N - zukkis - 355KH/s sustained solid

xintensity - 4
worksize - 256
gpu-engine - 1030
gpu-memclock - 1500
gpu-powertune - -20
gpu-threads - 2
thread-concurrency - 8193

Keccak - maxcoin - 350MH/s sustained -- 10% rejects

intensity - 14
worksize - 256
gpu-engine - 1125
gpu-memclock - 1020
gpu-powertune - -20
gpu-threads - 2

no thread-concurrency defined.

[KSGuy]

Very nice miner, I may have to setup my GPU again just so I can test this out.
Thanks for all the work OP!

[mannyg]

Following up from my last post, my other rig:

3 x 290 MSI Gaming 4G
These GPU's have their quirks.  I've found that removing the setx commands from my bat file and removing the environment variables for X11/X13 have improved its performance.  This rig doesnt handle switching well at all with any algorithm.  It's very hit or miss, even when switching X11>X13 and back.  Lowering the thread-concurrency for Scrypt/Scrypt-N resolved the error enqueing -4 error

X11 - darkcoin-mod  3.75MH/s sustained solid
X13 - marucoin-mod 2.85MH/s sustained solid

    intensity - 19
    worksize - 512
    gpu-engine - 1060
    gpu-memclock - 1250
    gpu-powertune - 10
    gpu-threads - 2
    hamsi-expand-big - 1

I'm not defining a thread concurrency for X11/X13.  Is it even necessary? I do define shaders - 2560 though.

Scrypt - zukkis - 850KH/s sustained solid
Scrypt-N - zukkis - 430KH/s sustained solid

    intensity - 19
    worksize - 512
    gpu-engine - 1000
    gpu-memclock - 1250
    gpu-powertune - 10
    gpu-threads - 1
    thread-concurrency - 20480

Keccak - maxcoin - 430MH/s sustained -- 10% rejects

    intensity - 14
    worksize - 256
    gpu-engine - 1080
    gpu-memclock - 1250
    gpu-powertune - 10
    gpu-threads - 1

no thread-concurrency defined.

[Lucky - Luciano]

Am I the only one who sees the ridiculousness of these performance improvements with increased power usage?

Sure, the early adopters get an advantage over those who haven't used the new technology yet.   In the long run, however, everyone will be using them.   This means difficulty goes up, and we're back where we were before, except now with higher energy costs and hotter graphics cards.  Less profits for all (except the energy companies)! Hooray!

  I agree.Hooray!Hooray!Hooray!

[atp1916]

Am I the only one who sees the ridiculousness of these performance improvements with increased power usage?

Sure, the early adopters get an advantage over those who haven't used the new technology yet.   In the long run, however, everyone will be using them.   This means difficulty goes up, and we're back where we were before, except now with higher energy costs and hotter graphics cards.  Less profits for all (except the energy companies)! Hooray!

Nope, don't agree.  It is not rational to think that a 290 @ 2.5mhs is "optimized" when a 750 Ti is pulling in the same hash rate vicinity but spending only 30w doing so.

With clocks exactly the same / drivers exactly the same, the optimized lasybear / sgminer v5 builds fall within 5-10% power usage (more) of the most current phm build on all my 290, 270, 280x, and 7950 rigs. Temps are virtually the same (including VRMs).  I do not use 5/6xxx cards, so it may be different with those architectures.

My take is that X11 has simply been under-optimized for AMD hardware since phm stopped developing a while back.  These current enhancements are bringing the performance up to where it should be.  

[platinum4]

Am I the only one who sees the ridiculousness of these performance improvements with increased power usage?

Sure, the early adopters get an advantage over those who haven't used the new technology yet.   In the long run, however, everyone will be using them.   This means difficulty goes up, and we're back where we were before, except now with higher energy costs and hotter graphics cards.  Less profits for all (except the energy companies)! Hooray!

Nope, don't agree.  It is not rational to think that a 290 @ 2.5mhs is "optimized" when a 750 Ti is pulling in the same hash rate vicinity but spending only 30w doing so.

With clocks exactly the same / drivers exactly the same, the optimized lasybear / sgminer v5 builds fall within 5-10% power usage (more) of the most current phm build on all my 290, 270, 280x, and 7950 rigs. Temps are virtually the same (including VRMs).  I do not use 5/6xxx cards, so it may be different with those architectures.

X11 has simply been under-optimized for AMD hardware since phm stopped developing a while back.  These current enhancements are bringing the performance up to where it should be.  

Optimized or not, hashrates are better right now for most AMD miners that have been following along with the x11mod/x13mod updates.  Anybody who has complaints should go back to sgminer 4.1.0 or sph-sgminer without modded kernels, and appreciate exactly how far the fuck we have come in eight weeks.

[tc61]

does this ave nvida support or just amd?

[jimlite]

I'd be very carefull with the X15 AMD miner floating around,
it could be trojan/virus.