|
Title: XMR-STAK 2.7.1 (CN-Heavy optimisations / Auto-tune / Bittube fix) Post by: RyoCurrency on December 10, 2018, 08:48:33 PM https://i.redd.it/npoiant4o4221.png
New version of xmr-stak 2.7.1 is available for download. This update brings you following: - Bittube fix(over 2.7.0 version) - Auto-tune function of intensity. When enabled - miner will try different intensities and lock on the best performing. The step of adjustment is configurable. - Adjustable interleaving function (suitable for dual-threaded configs). - Added "strided_index" value - 3. - Optimizations for AMD GPU-s (up to +15% in hashrate in CN-heavy compared with previous version ). - Optimizations for NVIDIA GPU-s. - Auto-generated config for AMD Vega is now dual-threaded. - bugfixes. Download: https://github.com/fireice-uk/xmr-stak/releases (https://github.com/fireice-uk/xmr-stak/releases) Updated miner docs: Github (https://github.com/fireice-uk/xmr-stak/blob/master/doc/tuning.md) Sharing is caring! Quote Help other miners, or request help: share your miner GPU config + overclock parameters + memory type + driver version + OS in this thread and post resulted hashrate. Title: Re: XMR-STAK 2.7.1 (CN-Heavy optimisations / Auto-tune / Bittube fix) Post by: RyoCurrency on December 10, 2018, 08:50:14 PM Gigabyte Vega 56 (Reference)
Gpu: 1600/950mV Mem: 950/950 Samsung OS: W10 + 18.6.1 CN-Heavy (Ryo): 1810h/s Quote "gpu_threads_conf" : [ { "index" : 0, "intensity" : 896, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 8, "unroll" : 8, "comp_mode" : false, "interleave" : 40 }, { "index" : 0, "intensity" : 896, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 8, "unroll" : 8, "comp_mode" : false, "interleave" : 40 }, ], "auto_tune" : 0, "platform_index" : 0, rx550-2G baffin, elpida. one-click timings. Win7x64, AMD 17.7.2 OC: 1200/1900 Quote // gpu: Baffin compute units: 10 // memory:960|1792|1920 MiB (used per thread|max per alloc|total free) { "index" : 1, "intensity" : 232, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 2, "unroll" : 8, "comp_mode" : true, "interleave" : 40 }, { "index" : 1, "intensity" : 232, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 2, "unroll" : 8, "comp_mode" : true, "interleave" : 40 }, CN- heavy: 415hs R7 260X: Quote // gpu: Bonaire compute units: 14 // memory:960|1344|1920 MiB (used per thread|max per alloc|total free) { "index" :1, "intensity" : 232, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 2, "unroll" : 8, "comp_mode" : true, "interleave" : 40 }, { "index" : 1, "intensity" : 232, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 2, "unroll" : 8, "comp_mode" : true, "interleave" : 40 }, Win7, AMD: 17.7.2, elpida OC: 1200/1600 CN-heavy, 3 cards: 240 - 280 h/s per card Title: Re: XMR-STAK 2.7.1 (CN-Heavy optimisations / Auto-tune / Bittube fix) Post by: RyoCurrency on December 10, 2018, 08:54:56 PM XFX Radeon R9 285 Black Edition 2gb
OS: HiveOS Mem: Elpida EDW2032BBBG 113-285A-CDFX-W83-106 Gpu: 1000mhz / Mem: 1400mhz 390h/s Quote "gpu_threads_conf" : [ // gpu: Tonga compute units: 28 // memory:909|1714|1818 MiB (used per thread|max per alloc|total free) { "index" : 0, "intensity" : 252, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 8, "unroll" : 8, "comp_mode" : false, "interleave" : 40 }, // gpu: Tonga compute units: 28 // memory:909|1714|1818 MiB (used per thread|max per alloc|total free) { "index" : 0, "intensity" : 252, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 8, "unroll" : 8, "comp_mode" : false, "interleave" : 40 }, Sapphire Rx470 4Gb Mining Edition Gpu: 1300/925mV Mem: 2000mhz / Samsung OS: Ubuntu/ AMD 17.40 CN-Heavy (Ryo): 900h/s Quote // gpu: Ellesmere compute units: 32 // memory:1978|4048|3957 MiB (used per thread|max per alloc|total free) { "index" : 5, "intensity" : 488, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 18, "unroll" : 8, "comp_mode" : false, "interleave" : 40 }, // gpu: Ellesmere compute units: 32 // memory:1978|4048|3957 MiB (used per thread|max per alloc|total free) { "index" : 5, "intensity" : 488, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 18, "unroll" : 8, "comp_mode" : false, "interleave" : 40 }, Sapphire Rx470 8Gb Gpu: 1300/925mV Mem: 2050mhz / Samsung Uber Mix 3.1.1 OS: Ubuntu/ AMD 17.40 CN-Heavy (Ryo): 1280h/s Quote { "index" : 0, "intensity" : 1000, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 8, "unroll" : 8, "comp_mode" : false, "interleave" : 40 }, { "index" : 0, "intensity" : 1000, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 8, "unroll" : 8, "comp_mode" : false, "interleave" : 40 }, RX 470 4Gb Nitro+ Gpu: 1300/900mV Mem: 2020mhz / Elpida EDW4032BABG 113-2E353AU.O4C OS: HIVEOS CN-Heavy (Ryo): 940h/s Quote // gpu: Ellesmere compute units: 32 // memory:1937|3771|3875 MiB (used per thread|max per alloc|total free) { "index" : 0, "intensity" : 480, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 2, "unroll" : 8, "comp_mode" : true, "interleave" : 40 }, // gpu: Ellesmere compute units: 32 // memory:1937|3771|3875 MiB (used per thread|max per alloc|total free) { "index" : 0, "intensity" : 480, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 2, "unroll" : 8, "comp_mode" : true, "interleave" : 40 }, ASUS (MINING-RX470-4G-LED-S) Radeon RX 470 Gpu: 1270/870mV Mem: 2050mhz / Samsung K4G41325FE 115-D009PI0-101 OS: HIVEOS CN-Heavy (Ryo): 900h/s Quote // gpu: Ellesmere compute units: 32 // memory:1964|3816|3928 MiB (used per thread|max per alloc|total free) { "index" : 1, "intensity" : 488, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 2, "unroll" : 8, "comp_mode" : true, "interleave" : 40 }, // gpu: Ellesmere compute units: 32 // memory:1964|3816|3928 MiB (used per thread|max per alloc|total free) { "index" : 1, "intensity" : 488, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 2, "unroll" : 8, "comp_mode" : true, "interleave" : 40 }, Title: Re: XMR-STAK 2.7.1 (CN-Heavy optimisations / Auto-tune / Bittube fix) Post by: polkovnik on December 11, 2018, 01:30:10 AM please advice what wrong
4 cards, Gpu 3 - Vega 64 1450/1050 Mhz Adrenaline 18.5.1 sorry, can't attach a picture, https://cdn1.savepice.ru/uploads/2018/12/11/6037d421607d9c2a50ec15254700c582-full.jpg gpu_threads_conf : [ // gpu: gfx900 compute units: 64 // memory:4024|4048|8048 MiB (used per thread|max per alloc|total free) { "index" : 3, "intensity" : 2008, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 8, "unroll" : 8, "comp_mode" : false, "interleave" : 40 }, // gpu: gfx900 compute units: 64 // memory:4024|4048|8048 MiB (used per thread|max per alloc|total free) { "index" : 3, "intensity" : 2008, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 8, "unroll" : 8, "comp_mode" : false, "interleave" : 40 }, ], auto_tune : 0, platform_index : 0, hashrate is 0 ??? Title: Re: XMR-STAK 2.7.1 (CN-Heavy optimisations / Auto-tune / Bittube fix) Post by: netmebtc on December 11, 2018, 09:25:19 AM Gigabyte Vega 56 (Reference) Gpu: 1600/950mV Mem: 950/950 Samsung OS: W10 + 18.6.1 CN-Heavy (Ryo): 1810h/s Quote "gpu_threads_conf" : [ { "index" : 0, "intensity" : 896, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 8, "unroll" : 8, "comp_mode" : false, "interleave" : 40 }, { "index" : 0, "intensity" : 896, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 8, "unroll" : 8, "comp_mode" : false, "interleave" : 40 }, ], "auto_tune" : 0, "platform_index" : 0, rx550-2G baffin, elpida. one-click timings. Win7x64, AMD 17.7.2 OC: 1200/1900 Quote // gpu: Baffin compute units: 10 // memory:960|1792|1920 MiB (used per thread|max per alloc|total free) { "index" : 1, "intensity" : 232, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 2, "unroll" : 8, "comp_mode" : true, "interleave" : 40 }, { "index" : 1, "intensity" : 232, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 2, "unroll" : 8, "comp_mode" : true, "interleave" : 40 }, CN- heavy: 415hs R7 260X: Quote // gpu: Bonaire compute units: 14 // memory:960|1344|1920 MiB (used per thread|max per alloc|total free) { "index" :1, "intensity" : 232, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 2, "unroll" : 8, "comp_mode" : true, "interleave" : 40 }, { "index" : 1, "intensity" : 232, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 3, "mem_chunk" : 2, "unroll" : 8, "comp_mode" : true, "interleave" : 40 }, Win7, AMD: 17.7.2, elpida OC: 1200/1600 CN-heavy, 3 cards: 240 - 280 h/s per card Can this parameter be used on version 2.7.0 ? Title: Re: XMR-STAK 2.7.1 (CN-Heavy optimisations / Auto-tune / Bittube fix) Post by: RyoCurrency on December 11, 2018, 09:37:07 AM Can this parameter be used on version 2.7.0 ? which one exactly? it is a list of configs as example. when you run first time stak, it generates config based on your system itself. then if you feel your gpus can do more, you need to slightly fine tune it. Title: Re: XMR-STAK 2.7.1 (CN-Heavy optimisations / Auto-tune / Bittube fix) Post by: RyoCurrency on December 11, 2018, 03:34:19 PM HIVEOS UPDATE
0.6-06@181211-2linux 2018-12-11 xmr-stak 2.7.0 patch fixed issue with BitTube (same as v2.7.1) https://hiveos.farm/changelog/ |
