Topic: WildRig Multi 0.35.1 beta 2 multi-algo miner for AMD & NVIDIA - page 62. (Read 92264 times)

I sent you a PM about this

If there any open reference implementation, I can take a look on it.

Alright.
Can you add 5 new algos?

Hi,

Unfortunately this is closed source project

Released 0.12.1.1 hotfix
- fixed hashrate printing per gpu

Hey there!

Any source code available?
I would contribute 5 algorithms of the GlobalToken hardfork (brand-new)

Thank you!

Released 0.12.1 beta
- added bitcore(timetravel10) algo
- improved hashrate for x16r/x16s/hex algo's when fugue, whirlpool, or skein is first in hashorder
- slight hashrate increase for all algo's where fugue used(e.g. bcd, renesis, a bit higher increase for sonoa and hmq1725)
- implemented colorized hashorder printing for some algo's
- implemented --benchmark parameter
- reworked --opencl-threads, now will work with --opencl-devices correctly
- fixed custom algo support in HiveOS

known issue: seems I have introduced new bug - not working per-card hashrate printing in console(only first card will show hashrate). I will release hotfix tomorrow. Anyway, total hashrate is working and API works too.

majika, Kind Sir, Thank you so much...

I should have known that my undervolts were the first place to start. I literally had them so carefully tuned down for cryptonight that even 25mv lower on any one card and the system was unstable. So I should have know I would have to work them down again for a new algo.

I bumped them all back up to 1v and I can get ~10Mh/s from the Vega56's and 11 from the 64's. I am still playing around.

Things I have found so far:

- 3 threads is a no go, no matter how low the intensity is set. System crashes immediately.
- I can run intensity at one setting higher for single thread. Hash rates are similar single or dual at highes stable intensity.
- lowering the memory clock a bunch from my CN settings didn't hurt performance at all.

I'm still experimenting but I at least can hash stable now.

Thanks again

Here's what I have so far with a non-reference 290x with a failing water block on it.  These were done using the parameters for rx570/rx580 so they are not optimal at all.  

bcd not done yet
c11   6.46 MH/s
geek not done yet
hex not done yet
hmq1725   2.56 MH/s
phi   5.41 MH/s
renesis not done yet
sonoa   700.18 KH/s
timetravel   12.58 MH/s
tribus   23.64 MH/s
x16r   6.22 MH/s
x16s   4.43 MH/s
x17   4.41 MH/s

lol.. now im seeing the kernels in the OP.
Cheer's melloyellow for heads up & Andrucrypt for the fine work



-- Yeah most def. shall do.. I've not mined on the 290Xs rig for quite some time. I was doing some XMR mining ages ago with them. I will bring them out of retirement to run a few tests across the algo's supported with wildRig miner & report back (asap). 

Awesome.  Let me know what you works for you.  I'll add those parameters in when I get a chance to see what happens and report back.

Those generated names are likely from sgminer compiling bins for scrypt or scrypt-n or darkcoin or something along those lines.  Andrucrypt gave us the kernels in the optional download so make sure you grab that.

Your 290x's work great on cryptonight algos, by the way, if you're not using them at all.

I am just about to blow the dust off my old Sapphire R9 290X TRIXX GPU's and run Wildrig-multi miner on these algo's (Test first if its even possible to run.) if so I will try help.

I have a good feeling about the 290x's mining HEX. I think they will smash that algo. idk need to test.

FYI names of my old generated kernels from back in the day using my gpus/older rigs. "Hawaiig2tc12404w256l4" & "Pitcairnglg2tc12404w256l4" FWIT

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: 20, worksize: 64/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 + HEX
[15:29:33] donation: 2%
[15:29:33] strategy: 1
[15:29:33] send-stale: no
[15:29:33] watchdog: enabled
[15:29:33] good-risers: default

Hashrate as reported on pool. 3.0909% 110 Mh/s   <===


Algo: x16s
GPU: 10 RX580 8GB Special Editions NITRO+ @ 1430mhz/2100 @ BIOS Mod to 1750 mhz timing straps.

[15:29:33] speed 10s/60s/15m 99989 83536 74286 kH/s max: 101575 kH/s


Notes.
I have am able to achieve much higher Hash Rates However, The increase to a higher Thread count to 3/4
Increase in Intensity (above 21,22,23) makes my rig become unstable and crashes after 20-30mins of mining.

The above is stable over 12hrs.
--opencl-threads 3 --opencl-launch 21x256 --strategy=0 --opencl-affinity=4 ~ 147MH/s

---

Algo: HEX



POOLSIDE STATS
Summary   Miners   Shares        Hashrate*         Reject*
hex            1           50.2399%   81.4 Mh/s         0%

Worker                Details                  Extra             Algo      Diff     Hashrate*        Reject*
RX580RIG1         WildRig/0.12.0    c=XDNA       hex      24      81.4 Mh/s        0



NB

:: speed 10s/60s/15m 120582 114144 90425 kH/s max: 147196 kH/s  <===
147MH/s is easily achievable but its hard to mine longer than 30mins stable/without crashing. (Will need to keep tweaking things) perhaps mess with powertune 0~+10%.
increase with a touch of memory 'or' core voltage (-cvddc -mvddc) to see if this will help with stability.  idk.. ??

Does anything special need to be done in order for Hawaii cards to run besides downloading the optional bin.  I'm benchmarking WildRig Multi in RainbowMiner and can't get any shares?
It might be because --opencl-threads  --opencl-launch are not set by default in RainbowMiner.
Does anybody have any good thread, intensity, and worksize settings for a 290x?

Hi,

currently my scripts don't support "algo" parameter from HiveOS GUI(will fix this in next release), so it should work using "--algo bcd" string in extra-parameters. What error miner shows exactly? Any screen?

Still not considering rocm? I have another miners on rocm and can't really be switching to amdgpu-pro just to try this on on vega rig.

Hi,

I tried the v12 beta version on Hive OS but although I had selected the algo name from the known algos (e.g. bcd, x17 etc.), it consistently takes the "aergo" as the default algorithm. I also tried to add "--algo bcd" switch into the extra parameters field, but this time gives incorrect parameter error. It works fine with aergo but as you may know the pool is different, so it gets rejected by the pool.

I wrote to Hive OS support but they wrote that it was due to the miner's limited support to Hive OS and being a beta version etc.

What am I doing wrong? Any suggestion would be really aprreciated.

Hive OS Custom Miner Settings: https://ibb.co/fOB9op
Hive OS Miner Log: https://ibb.co/eV3Eop

Thx

your intensity maybe a bit high also you could specify your worksize (--opencl-launch=22)  0,64,128,256

Give this a try.

> wildrig.exe --algo hex --opencl-platform=1 --opencl-threads 2 --opencl-launch 21x128 --strategy=1

Next try

> wildrig.exe --algo hex --opencl-platform=1 --opencl-threads 3 --opencl-launch 21x256 --strategy=0

.. etc..
Take speed readings of hashrate faster 300 shares or whatever. leave it run to get a good avg. (not just peek)
Rinse & repeat.

I haven't done much reading up on either HEX algo nor, Phi algo so I need to find out what exactly either of the algo's prefer.

- Are HEX | Phi memory intensive ?
- Does the Engine speeds affect the hashing of the algo's above?
- Can GPU engine speeds be reduced to save on power (as an example) Drop Core from max to 80% of max without it affecting hashrates.

These are all questions which I must learn more about. its always good to understand deeper as opposed to blindly setting mining parameters/options.

The name of the game is to mine the fastest speeds in the most efficient manner.


The only thing I can go on to help is to watch the hashrates on your miner if you see them bouncing around a lot after a couple of hundred shares have gone past lower your intensity.

Your Vega GPU's run HBM2 memory as opposed to RX470/80 570/80 GDDR5 so the settings I found work best will obviously be different to yours. However, i understand you are seeking baselines. As per your initial question.

Perhaps you can figure things out best by working backwards.

Start with lowest settings of everything
1 Thread
0 worksize
18 intensity
0 stratagy

Then ramp your settings up.
pick one setting to focus your benchmark on then increase. once you found fastest. sweetspot pick the next setting then ramp than up and so on.

Once that is done you can test with the Strategy=0|1 option.
--Independent GPU's over multi-gpu as one device.

As was said previously by someone its had to actually benchmark as the algos change.
An option could be to benchmark in sgminer-kl or whatever other miner to find exact best speeds using the "--benchmark BBBBBBBB" <<= (change to match hex algo)

Find a miner where you are able to issue the --benchmark command.

Finding optimal settings in that miner and then port/copy your findings /config over into wildrig (for as close as possible match) [Just a suggestion ;]

Good Luck.

I will post my fastest settings for all the algos when I have a finished.
FYI:

I also undervolt and down clock Core speeds for ETH. But sometimes I forget and start to mine another algo. Phi|Hex|X16r etc and my undervolting causes miners to crash. -- just a FYI kind of thing

OK, I have it running stable now for 15 minutes.
Using the following bat file

 GPUs seems to be running at about max load, for hex it obviously fluctuates but hangs in the 90+ % range most of the time and wattage per GPU is reading ~100-120w.
Hashrate is ~10.2Mh/s per GPU.   My undervolt and clock speeds are still set where they were optimal for Cryptonight algo.


ANY further help here will be greatly appreciated 

Hi,

 I am new to this software, also new to any other algo than CN. I've been mining with my 9 card RX Vega rig on XMR for a loooong time and wanted to give something new a try.

I have been playing with WildRig for a bit today trying to get it stable on my Vega rig.

I would greatly appriciate a baseline for settings to try.  Intensity? Threads? Worksize? Etc.

I was able to get it hashing for almost 10 minutes with this config from the post by majika


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

Thanks,
Biker