WildRig Multi 0.40.5 multi-algo miner with low dev-fee (AMD/NVIDIA/INTEL)

[andrucrypt]

I'll test it tonight, have a pair of Pitcairns too
How long to run in "benchmark" mode for reliable results? Is 2 minutes ok ?

there is still no benchmark mode unfortunately, so use real pools and wallets 2-5minutes should be ok, but to be sure that it works - there should be accepted shares.

[1715680791]

1715680791

[1715680791]

1715680791

[restless]

Adding some results for Pitcairn and Tahiti
everything worked out-of-the-box - great job!
Obviously, if you ever want to, speed can be optimised - cards were not very hot. Everywhere used "safe settings" - 2 threads instead of 3, no attempt to choose --opencl-launch parameter - any hint if trying different settings (and what...) is worth the try?

Code:

SUPPORTED ALGORITHMS and BENCHMARKS:							
	   RX460        RX470             RX570        RX580            R265	R270	 R7950
bcd	~3.5 MH/s	~8.1 MH/s	~8.4 MH/s	~10.2 MH/s	2.4	2.6	3.75
c11	~4.1 MH/s	~9.5 MH/s	~9.7 MH/s	~11.8 MH/s	2.8	3.1	4.7
geek	~4.7 MH/s	~10.8 MH/s	~11.2 MH/s	~13.5 MH/s	3.25	3.6	5.2
hex	  n/a*	          n/a*	          n/a*	           n/a*	        1.5	1.75	2.3
hmq1725	~1.8 MH/s	~4.2 MH/s	~4.3 MH/s	~5.3 MH/s	1.05	1.116	1.7
phi	~4.9 MH/s	~11.1 MH/s	~11.4 MH/s	~14.1 MH/s	1.9	2.25	3.3
renesis	~4.2 MH/s	~10.4 MH/s	~10.7 MH/s	~12.9 MH/s	1.67	1.9	2.7
sonoa	~450 kH/s	~1050 kH/s	~1060 kH/s	~1290 kH/s	315	355	500
timetravel ~6.9 MH/s	~17.8 MH/s	~17.6 MH/s	~21.6 MH/s			
tribus	~13.0 MH/s	~29.7 MH/s	~30.5 MH/s	~37.6 MH/s	11	12	17.5
x16r	      n/a**	  n/a**	          n/a**	        n/a             1.9	2.1	3.45
x16s	      n/a**	  n/a**	          n/a**	        n/a**           1.8	2	2.9
x17	~2.9 MH/s	~6.7 MH/s	~6.9 MH/s	~8.3 MH/s	1.85	2.05	2.9
bitcore					                              1300000 1300000  3050000

All results are after running for 2 minutes. All cards run @ stock clocks eg, 265 is @900/1250, 270 is @1000/1350, 7950 were @900/1250

[andrucrypt]

Adding some results for Pitcairn and Tahiti
everything worked out-of-the-box - great job!
Obviously, if you ever want to, speed can be optimised - cards were not very hot. Everywhere used "safe settings" - 2 threads instead of 3, no attempt to choose --opencl-launch parameter - any hint if trying different settings (and what...) is worth the try?

Code:

SUPPORTED ALGORITHMS and BENCHMARKS:							
	   RX460        RX470             RX570        RX580            R265	R270	 R7950
bcd	~3.5 MH/s	~8.1 MH/s	~8.4 MH/s	~10.2 MH/s	2.4	2.6	3.75
c11	~4.1 MH/s	~9.5 MH/s	~9.7 MH/s	~11.8 MH/s	2.8	3.1	4.7
geek	~4.7 MH/s	~10.8 MH/s	~11.2 MH/s	~13.5 MH/s	3.25	3.6	5.2
hex	  n/a*	          n/a*	          n/a*	           n/a*	        1.5	1.75	2.3
hmq1725	~1.8 MH/s	~4.2 MH/s	~4.3 MH/s	~5.3 MH/s	1.05	1.116	1.7
phi	~4.9 MH/s	~11.1 MH/s	~11.4 MH/s	~14.1 MH/s	1.9	2.25	3.3
renesis	~4.2 MH/s	~10.4 MH/s	~10.7 MH/s	~12.9 MH/s	1.67	1.9	2.7
sonoa	~450 kH/s	~1050 kH/s	~1060 kH/s	~1290 kH/s	315	355	500
timetravel ~6.9 MH/s	~17.8 MH/s	~17.6 MH/s	~21.6 MH/s			
tribus	~13.0 MH/s	~29.7 MH/s	~30.5 MH/s	~37.6 MH/s	11	12	17.5
x16r	      n/a**	  n/a**	          n/a**	        n/a             1.9	2.1	3.45
x16s	      n/a**	  n/a**	          n/a**	        n/a**           1.8	2	2.9
x17	~2.9 MH/s	~6.7 MH/s	~6.9 MH/s	~8.3 MH/s	1.85	2.05	2.9
bitcore					                                        1300000	1300000	3050000

All results are after running for 2 minutes. All cards run @ stock clocks eg, 265 is @900/1250, 270 is @1000/1350, 7950 were @900/1250

Thanks for testing! But I have a question - was there any accepted shares? Because I have a report that there was no shares at all ( And that probably because of big endian architecture, which is not tested in my kernels and I need sample of card to fix that...

[restless]

Not sure... I mostly automated the test:
start wildrig.exe ... -l algo.log
timeout /t 120
taskkill
start wildrig

Will check logs and post

PS: it seems no accepted shares.
I will rerun the tests using settings from post1 in the topic

[Docice]

when is it planned to add cpu algo?

[MetalHelmet]

Can I ask for help with setup wildrig-multi in HiveOS

When I set "Hash algorithm: " to bcd and leave "Extra config arguments: " empty - I'm getting rejected shares "Invalid share" (seems wrong algo selected - it select's aergo by default)

When I set "Hash algorithm: " to --- and put "algo": "bcd" into "Extra config arguments:" field - i get error " ./wildrig-multi: unsupported non-option argument '"algo":'"

What parameters should I set for   "Hash algorithm: " or / and for "Extra config arguments:" to mine BCD  ?

[andrucrypt]

Can I ask for help with setup wildrig-multi in HiveOS

When I set "Hash algorithm: " to bcd and leave "Extra config arguments: " empty - I'm getting rejected shares "Invalid share" (seems wrong algo selected - it select's aergo by default)

When I set "Hash algorithm: " to --- and put "algo": "bcd" into "Extra config arguments:" field - i get error " ./wildrig-multi: unsupported non-option argument '"algo":'"

What parameters should I set for   "Hash algorithm: " or / and for "Extra config arguments:" to mine BCD  ?

Hm, seems I need to improve my scripts for HiveOS a bit. But you can configure everything using "Extra config arguments". They are command-line, not json So just put there:

Code:

--algo bcd --opencl-launch=18x0

What about --opencl-launch - it can be different, check optimal parameters table and maybe experiment for your cards. Also on moment - currently HiveOS will show wrong hashrate in GUI because of bug in my API. Today I will release a fix.

when is it planned to add cpu algo?

Currently have no plans to work on them.

[SecretRecipe]

Question:
Has anyone figured out any specific arguments that can be used to increase x16r hashrate?

[andrucrypt]

Released 0.12.0 beta
- slight speedup for bcd
- fixed API for showing correct hashrate when use --opencl-threads
- stripped kernels

[TasosRiv]

Released 0.12.0 beta
- slight speedup for bcd
- fixed API for showing correct hashrate when use --opencl-threads
- stripped kernels

What does "stripped kernels" mean?

[majika]

Question:
Has anyone figured out any specific arguments that can be used to increase x16r hashrate?

Ok to answer your question a little overview on my test rig
Test rig#1  ASUS B250 19pcie, 1600w + 1200 w PSU(s) + x10 Sapphire RX580 8gb NITRO+ Special Editions 1430Mhz/2250Mhz -0.50mV

I produce on Raven X16r algo ~ 9 - 11MH/s per card

Code:

 donation: 2%
[20:45:25] strategy: 0
[20:45:25] send-stale: no
[20:45:25] watchdog: enabled
[20:45:25] good-risers: default
[20:45:25] compiling code and initializing GPUs. This will take a while...
[20:45:25] GPU #0 [BusID: #1] Radeon RX 580 Series
[20:45:25] kernel: Ellesmere, intensity: 23, worksize: 256/256, cu: 36

accepted(123/0) diff 3.68G avg. effort 98.43% (24 ms)
[21:02:27] GPU #0: 10s/60s/15m 9412 10069 7783 kH/s
[21:02:27] GPU #1: 10s/60s/15m 9350 9878 7839 kH/s
[21:02:27] GPU #2: 10s/60s/15m 9290 9870 7833 kH/s
[21:02:27] GPU #3: 10s/60s/15m 9318 9889 8042 kH/s
[21:02:27] GPU #4: 10s/60s/15m 9424 10001 7868 kH/s
[21:02:27] GPU #5: 10s/60s/15m 9284 9885 7800 kH/s
[21:02:27] GPU #6: 10s/60s/15m 9420 10008 7926 kH/s
[21:02:27] GPU #7: 10s/60s/15m 9427 9901 7694 kH/s
[21:02:27] GPU #8: 10s/60s/15m 9427 9931 7729 kH/s
[21:02:27] GPU #9: 10s/60s/15m 9295 9882 7776 kH/s
[21:02:27] speed 10s/60s/15m 93651 99318 78294 kH/s max: 150644 kH/s

Code:

[21:10:27] speed 10s/60s/15m 90200 89931 81527 kH/s max: 150644 kH/s
[21:10:29] accepted(165/0) diff 560.63M avg. effort 104.35% (24 ms)
[21:10:42] Stratum set difficulty to 20.0495
wildrig.exe --algo x16r --url=stratum+tcp://<URL>:6667 --user=XXXXXXXXXX.tRIG011 --pass=xxxx --opencl-platform=1 --opencl-threads 4 --opencl-launch 23x256 --watchdog

I plan to test different intensity:worksize combinations/settings and will report back.
--opencl-threads > 2,3,4
and play around with  --strategy=1 (if this will do anything or not) currently with those hashrates above "strategy: 0" was set.
Idk how many different --Strategy options there are 0,1,2,n...

I may split the devices over like 3 miner instances using the "--multiple-instance" option and changing the threads this way to also check on faster hashrates.

FYI:

Im seeing lots of these:-

Code:

[21:14:26] GPU #26: yay! found 2 shares at once

**checkout the GPU count #26 ??*
Im only running 10 gpu's in this rig. it could be due to the of threads (4) I have set. idk..  

This is far from optimal settings and lots more tweaks to report/log. BUT HTH

Thanks for this great miner andrucrypt; its faster than Avermore 1.4.1 and is a whole lot more stable miner for me anyway


==UPDATE==

Code:

23:25:01] GPU #0: 10s/60s/15m 13183 14256 9491 kH/s
[23:25:01] GPU #1: 10s/60s/15m 12824 14086 9332 kH/s
[23:25:01] GPU #2: 10s/60s/15m 12927 14092 9390 kH/s
[23:25:01] GPU #3: 10s/60s/15m 12965 14260 9422 kH/s
[23:25:01] GPU #4: 10s/60s/15m 13286 14376 9500 kH/s
[23:25:01] GPU #5: 10s/60s/15m 12774 13740 9268 kH/s
[23:25:01] GPU #6: 10s/60s/15m 13187 14113 9482 kH/s
[23:25:01] GPU #7: 10s/60s/15m 13344 14375 9512 kH/s
[23:25:01] GPU #8: 10s/60s/15m 13125 14269 9502 kH/s
[23:25:01] GPU #9: 10s/60s/15m 13028 14275 9395 kH/s
[23:25:01] speed 10s/60s/15m 130645 141847 94298 kH/s max: 184810 kH/s
[23:25:02] accepted(166/0) diff 1.35G avg. effort 115.63% (24 ms)

./wildrig.exe --algo x16r --opencl-platform=1 --opencl-threads 3 --opencl-launch 22x256 --strategy=0 --multiple-instance  --url=stratum+tcp://<POOL>:<PORT> --user=XXXXXXXXXX.tRIG011 --pass=x --print-full --watchdog

My Hashrate: 152.70 MH/s
148,782.83

[andrucrypt]

./wildrig.exe --algo x16r --opencl-platform=1 --opencl-threads 3 --opencl-launch 22x256 --strategy=0 --multiple-instance  --url=stratum+tcp://<POOL>:<PORT> --user=XXXXXXXXXX.tRIG011 --pass=x --print-full --watchdog

My Hashrate: 152.70 MH/s
148,782.83

I was going to write that 4 threads is too big amount, but seems you came with the same conclusion

**checkout the GPU count #26 ??*
Im only running 10 gpu's in this rig. it could be due to the of threads (4) I have set. idk.. 

Yeah, there still some places to fix that thing with few threads per gpu, because it shows thread id instead of gpu id.

What about strategy - that's experimental parameter came from original wildrig. 0 is default and divide nonce range(0..2^32) for all GPU's, so every GPU(or thread of it, if use --opencl-threads) work in its own range. Using strategy 1 all GPU's will work as one device - starting calculation from 0 to 2^32. In some cases that can give some advantage for amount of solved shares, but I didn't make any experiment, and for x16r this will be too hard

[majika]

Test RIG x10 Sapphire RX580 Special Editions 1430Mhz/2250Mhz BIOS modded from 1750 timing straps

AMD TEST RIG - Platform & Drivers.
Radeon Software Version - 17.11.2
Radeon Software Edition - Crimson ReLive
Windows Version - Windows 10 (64 bit)
System Memory - 8 GB
CPU Type - Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
GPU #0-9 Radeon RX 580 Series
kernel: Ellesmere, intensity: 23, worksize: 256/256, cu: 36


 * VERSIONS:     WildRig/0.12.0 beta libuv/1.21.0 OpenCL/2.0 MSVC/2015
 * CPU:          Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz x64 AES-NI
 * ALGO:         x16r
[16:01:42] donation: 2%
[16:01:42] strategy: 1
[16:01:42] send-stale: no
[16:01:42] watchdog: enabled
[16:01:42] good-risers: default  <== Will give this option a test under a few different configurations and report back.

Indeed, I like to try every combination to squeeze maximum performance out of my mining setup.
I try to be as methodical in my testing as possible. Ill keep posting my results and once complete I will post my tests here asap!
 with --opencl-threads 4 I tested lowering the Intensity and worksize but --opencl-threads 3 results are best for my setup. However the remaining variable which I need to duplicate some tests is with the  --strategy=1 changes (from --strategy=0).


I noticed with thread count set to --opencl-threads 4 (Worksize 256 and -I 23) makes it kind of choke up with stale shares, my rig seems much happier when it's set to --opencl-threads 3 (as per what was in the OP) in the examples.

so every GPU(or thread of it, if use --opencl-threads) work in its own range. Using strategy 1 all GPU's will work as one device

As for the --strategy=0 | --strategy=1

..interesting

So if i understand how it works it correct. Setting the --strategy switch to "=1"  the workload will be "attacked" and/or "Hashed" by all 10 GPU's in my rig working in unison as opposed to
--strategy=0 where each of the 10 GPU's process the workload independently as an individual, ungrouped device split among each of my 10 gpus . Excuse my crude description about how the --strategy switch is setup to work.. -- TY:)


Could this be why I see so many 2 shares found at once messages (whilst in  --strategy=1 mode:-

Code:

[15:12:26] GPU #11: yay! found 2 shares at once

============
S1t4i21w256
wildrig.exe --algo x16r --strategy=1 --opencl-platform=1 --opencl-threads 4 --opencl-launch 21x256

 

Code:

[15:49:37] GPU #0: 10s/60s/15m 11505 9405 7893 kH/s
[15:49:37] GPU #1: 10s/60s/15m 11288 9408 7848 kH/s
[15:49:37] GPU #2: 10s/60s/15m 11146 9315 7882 kH/s
[15:49:37] GPU #3: 10s/60s/15m 11087 9185 7839 kH/s
[15:49:37] GPU #4: 10s/60s/15m 11409 9312 7854 kH/s
[15:49:37] GPU #5: 10s/60s/15m 11363 9213 7777 kH/s
[15:49:37] GPU #6: 10s/60s/15m 11409 9409 7931 kH/s
[15:49:37] GPU #7: 10s/60s/15m 11601 9513 8014 kH/s
[15:49:37] GPU #8: 10s/60s/15m 11518 9596 7964 kH/s
[15:49:37] GPU #9: 10s/60s/15m 11191 9464 7819 kH/s
[15:49:37] speed 10s/60s/15m 113521 93841 78824 kH/s max: 164964 kH/s
[15:49:39] new job from rvn.xxxxxxxxxx.xxx:<port> diff 481.76M
[15:49:43] accepted(129/0) diff 481.76M avg. effort 106.48% (26 ms)
[15:49:46] accepted(130/0) diff 481.76M avg. effort 106.15% (26 ms)
[15:49:46] accepted(131/0) diff 481.76M avg. effort 105.38% (26 ms)
[15:49:57] accepted(132/0) diff 481.76M avg. effort 106.40% (25 ms)
[15:49:58] accepted(133/0) diff 481.76M avg. effort 105.84% (26 ms)
[15:50:04] accepted(134/0) diff 481.76M avg. effort 106.02% (25 ms)
[15:50:13] Stratum set difficulty to 47.8576

S1t4i22w256
wildrig.exe --algo x16r --strategy=1 --opencl-platform=1 --opencl-threads 4 --opencl-launch 22x256

Code:

[16:22:32] accepted(131/0) diff 701.81M avg. effort 94.58% (27 ms)
[16:22:33] GPU #0: 10s/60s/15m 13323 13325 8186 kH/s
[16:22:33] GPU #1: 10s/60s/15m 12849 12989 8008 kH/s
[16:22:33] GPU #2: 10s/60s/15m 13001 13065 8036 kH/s
[16:22:33] GPU #3: 10s/60s/15m 12911 13126 8027 kH/s
[16:22:33] GPU #4: 10s/60s/15m 13063 12977 8123 kH/s
[16:22:33] GPU #5: 10s/60s/15m 12834 12892 8033 kH/s
[16:22:33] GPU #6: 10s/60s/15m 13298 13206 8189 kH/s
[16:22:33] GPU #7: 10s/60s/15m 13256 13345 8183 kH/s
[16:22:33] GPU #8: 10s/60s/15m 12844 13329 8127 kH/s
[16:22:33] GPU #9: 10s/60s/15m 12894 12996 8037 kH/s
[16:22:33] speed 10s/60s/15m 130277 131254 80953 kH/s max: 146829 kH/s
[16:22:36] Stratum set difficulty to 100.3928
[16:22:36] new job from rvn.xxxxxxxxxx.xxx:<port> diff 1.68G

S1t4i23w256
wildrig.exe --algo x16r --strategy=1 --opencl-platform=1 --opencl-threads 4 --opencl-launch 23x256

Code:

To many Stale shares... 

S1t3i23w256
wildrig.exe --algo x16r --strategy=1 --opencl-platform=1 --opencl-threads 3 --opencl-launch 23x256

Code:

[16:51:23] new job from rvn.suprnova.cc:6667 diff 2.55G
[16:51:24] GPU #0: 10s/60s/15m 8266 6643 8219 kH/s
[16:51:24] GPU #1: 10s/60s/15m 7800 6539 8096 kH/s
[16:51:24] GPU #2: 10s/60s/15m 8072 6593 8022 kH/s
[16:51:24] GPU #3: 10s/60s/15m 8119 6615 8089 kH/s
[16:51:24] GPU #4: 10s/60s/15m 8169 6669 8221 kH/s
[16:51:24] GPU #5: 10s/60s/15m 8071 6605 8105 kH/s
[16:51:24] GPU #6: 10s/60s/15m 8353 6456 8221 kH/s
[16:51:24] GPU #7: 10s/60s/15m 8163 6661 8259 kH/s
[16:51:24] GPU #8: 10s/60s/15m 8152 6718 8122 kH/s
[16:51:24] GPU #9: 10s/60s/15m 8011 6589 8036 kH/s
[16:51:24] speed 10s/60s/15m 81037 66092 81394 kH/s max: 132943 kH/s

My Hashrate: 92.91 MH/s



S1t3i22w256
wildrig.exe --algo x16r --strategy=1 --opencl-platform=1 --opencl-threads 3 --opencl-launch 22x256

Code:

[17:27:23] GPU #0: 10s/60s/15m 12011 8280 8435 kH/s
[17:27:23] GPU #1: 10s/60s/15m 12356 8144 8297 kH/s
[17:27:23] GPU #2: 10s/60s/15m 12028 8073 8291 kH/s
[17:27:23] GPU #3: 10s/60s/15m 12081 8194 8294 kH/s
[17:27:23] GPU #4: 10s/60s/15m 12367 8361 8407 kH/s
[17:27:23] GPU #5: 10s/60s/15m 12013 8288 8323 kH/s
[17:27:23] GPU #6: 10s/60s/15m 12036 8241 8418 kH/s
[17:27:23] GPU #7: 10s/60s/15m 12305 8364 8442 kH/s
[17:27:23] GPU #8: 10s/60s/15m 12233 8191 8390 kH/s
[17:27:23] GPU #9: 10s/60s/15m 11965 7961 8264 kH/s
[17:27:23] speed 10s/60s/15m 121400 82005 83567 kH/s max: 127720 kH/s
[17:27:33] Stratum set difficulty to 38.5909
[17:27:33] new job from rvn.xxxxxxxxxx.xxx:<PORT> diff 647.46M
[17:27:37] accepted(150/0) diff 647.46M avg. effort 103.02% (24 ms)
[17:27:50] accepted(151/0) diff 647.46M avg. effort 104.05% (24 ms)
[17:28:00] accepted(152/0) diff 647.46M avg. effort 104.74% (24 ms)

My Hashrate: 182.20 MH/s


S1t3i21w256
wildrig.exe --algo x16r --strategy=1 --opencl-platform=1 --opencl-threads 3 --opencl-launch 21x256

Code:

...

=============

ALGO: HEX  More settings to test and report back on. (ASAP!)

Code:

wildrig.exe --algo hex --opencl-platform=1 --opencl-threads 2 --opencl-launch 23x256 --strategy=0 --multiple-instance  --url= --user=.RX580RIG1 --pass=x --print-full --watchdog

Wildrig-multi is a BEAST at mining HEX Algo !!!

This is twice as fast as SGMiner-HEX (AMD)-v04.R Wildrig miner is a beast for HEX algo.
Im getting about 7.9~8.6MH/s per GPU -- POOL side reporting My Hashrate: 88.85 MH/s

Look at this also. Im finding LOADS of these 2 shares & some found 3 shares at once.

Code:

[19:43:18] GPU #1: yay! found 2 shares at once
[19:43:18] oops, stale share... ignore it
[19:43:18] GPU #9: yay! found 2 shares at once
[19:43:19] GPU #15: yay! found 2 shares at once

Code:

[19:25:16] GPU #0: 10s/60s/15m 8095 8131 n/a kH/s
[19:25:16] GPU #1: 10s/60s/15m 7958 7999 n/a kH/s
[19:25:16] GPU #2: 10s/60s/15m 7981 8013 7562 kH/s
[19:25:16] GPU #3: 10s/60s/15m 7989 8012 7573 kH/s
[19:25:16] GPU #4: 10s/60s/15m 8183 8145 7751 kH/s
[19:25:16] GPU #5: 10s/60s/15m 7952 7963 7552 kH/s
[19:25:16] GPU #6: 10s/60s/15m 8159 8140 7745 kH/s
[19:25:16] GPU #7: 10s/60s/15m 8034 8129 7761 kH/s
[19:25:16] GPU #8: 10s/60s/15m 8288 8284 7782 kH/s
[19:25:16] GPU #9: 10s/60s/15m 7927 8185 7631 kH/s
[19:25:16] speed 10s/60s/15m 80574 81005 69000 kH/s max: 81617 kH/s
[19:25:17] accepted(239/0) diff 82.72M avg. effort 109.48% (14 ms)
[19:25:18] accepted(240/0) diff 82.72M avg. effort 109.32% (14 ms)

--edit

I find " --strategy=0 " is faster than  "--strategy=1" (***For HEX**) But this could be coincidental and a lot more testing many more possible combinations before im 100%
Fastest HEX & X16r algos miner I have found for AMD rigs so far. Excellent work Dev

[andrucrypt]

About 2-3 shares per GPU - that depends on difficulty set by pool, lower difficulty and higher intensity - higher chance to get more than 1 share to be solved What about x16r algo - this is hard to find faster parameters because of random hashorder right now, without bench mode.

[ThePunisher49X]

About 2-3 shares per GPU - that depends on difficulty set by pool, lower difficulty and higher intensity - higher chance to get more than 1 share to be solved What about x16r algo - this is hard to find faster parameters because of random hashorder right now, without bench mode.

True. It all depends on the pool.
Can the above member say which pool he is using for conducting his test using the miner on HEX?

[majika]

yeah, as I start mining my shares fly up the mining console screen but as the diff adapts these occurrences slow down and then stops as pool diff is normalized.

i'm going through every setting no matter how silly it looks I want to be methodical as possible and go through every switch/option to find the sweet spot for each algo. tbh, whats already on the OP example is pretty much spot on. but on the HEX algo. Its the fastest miner I've used period!.

Regards the X16r I need to finish going over (repeating) tests with the --strategy=1 option enabled.

The Strategy experimental setting is an interesting concept to make the (*multi-gpu*) mining rig act as a single device. I think that's cool.
I have never came across something like this before. 

[majika]

About 2-3 shares per GPU - that depends on difficulty set by pool, lower difficulty and higher intensity - higher chance to get more than 1 share to be solved What about x16r algo - this is hard to find faster parameters because of random hashorder right now, without bench mode.

True. It all depends on the pool.
Can the above member say which pool he is using for conducting his test using the miner on HEX?

Test pool(s)
supranova

stratum+tcp://xdna.suprnova.cc:4919     0% fee atm [Primary]
stratum+tcp://rvn.suprnova.cc:6667       1.0 % fee [Primary]
stratum+tcp://eu.ravenminer.com:1111  0.9% fee [backup]

[edwinosky]

my test with something hex
 
GPU0 ASUS ROGSTRIX RX560 4GB
GPU1 MSI ARMOR RX570 8GB
GPU2 ASUS ROGSTRIX RX570 4GB
GPU3 MSI ARMOR RX480 4GB
GPU4 MSI GAMING RX580 4GB
GPU5 MSI ARMOR RX470 4GB

wildrig.exe --algo hex --opencl-threads 3 --opencl-launch 23x256 --strategy=0 --multiple-instance --print-full --url=stratum+tcp://xdna.suprnova.cc:4919 --user=USER.WORKER --pass=x

[andrucrypt]

my test with something hex
 
GPU0 ASUS ROGSTRIX RX560 4GB
GPU1 MSI ARMOR RX570 8GB
GPU2 ASUS ROGSTRIX RX570 4GB
GPU3 MSI ARMOR RX480 4GB
GPU4 MSI GAMING RX580 4GB
GPU5 MSI ARMOR RX470 4GB

wildrig.exe --algo hex --opencl-threads 3 --opencl-launch 23x256 --strategy=0 --multiple-instance --print-full --url=stratum+tcp://xdna.suprnova.cc:4919 --user=USER.WORKER --pass=x

Intensity 23 is too high for RX560 card, and that's why you get n/a on it. And worksize 256 is not optimal as I know. What about hashrate - seems you get worst hashorder. Today I will make some benchmarks with worst and best situations.

[TasosRiv]

…

Thank you Majika, I took the liberty to link your post about the HEX hashrate to our XDNA Ann thread!
https://bitcointalk.org/index.php?topic=4517612.msg46554102#msg46554102