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

[andrucrypt]

best stable for me atm (have to wait one hour minimum) is 2 threads and 17 intensity (11.2MH)
with auto settings i got 12.2MH but one card cant handle this and after some time the others follow

Well, auto-parameters are for those configuration I use when benchmarking, so with lower voltage/etc. it can be not the optimal one

[1714128153]

1714128153

[1714128153]

1714128153

[1714128153]

1714128153

[1714128153]

1714128153

[nordmann666]

best stable for me atm (have to wait one hour minimum) is 2 threads and 17 intensity (11.2MH)
with auto settings i got 12.2MH but one card cant handle this and after some time the others follow

Well, auto-parameters are for those configuration I use when benchmarking, so with lower voltage/etc. it can be not the optimal one

no problem...it works now and i can try some tweaking (some cards can 11,7 with 1450mhz set = 1400 effective) and others struggle with 1380 - but thats normal...i only have to know some save intens and i got it...thx again and i hope you devs will find ways to boost performance on Vega for nvidia dominated algos (1070 with 130W can reach 15-16mh on x21s - fxck)

[Ladydoge]

Hi. Does this miner need some special parameters to work with miningrigrentals? I use

wildrig.exe --print-full --algo hmq1725 --opencl-threads auto --opencl-launch auto --url us-central01.miningrigrentals.com:3333 --user username.rig --pass x
if ERRORLEVEL 1000 goto custom
timeout /t 5
goto loop

:custom
echo Some error happened, put custom command here
timeout /t 5
goto loop

and only get this

[4ward]

Hi. Does this miner need some special parameters to work with miningrigrentals? I use

wildrig.exe --print-full --algo hmq1725 --opencl-threads auto --opencl-launch auto --url us-central01.miningrigrentals.com:3333 --user username.rig --pass x
if ERRORLEVEL 1000 goto custom
timeout /t 5
goto loop

:custom
echo Some error happened, put custom command here
timeout /t 5
goto loop

and only get this

miningrigrentals redirect you to a different port, ask them why its not working

[andrucrypt]

Hi. Does this miner need some special parameters to work with miningrigrentals? I use

wildrig.exe --print-full --algo hmq1725 --opencl-threads auto --opencl-launch auto --url us-central01.miningrigrentals.com:3333 --user username.rig --pass x
if ERRORLEVEL 1000 goto custom
timeout /t 5
goto loop

:custom
echo Some error happened, put custom command here
timeout /t 5
goto loop

and only get this

Try to use correct port from start(it should be somewhere in your control panel). Don't know why, but right now miner get some wrong data from pool for reconnection(port 5 is definitely not good).

[Ladydoge]

^ Thanks. It works now.

[misterkit]

Is it possible to exit gracefully after a GPU has an issue?  I have a GPU that will occasionally hang/stop reporting (due to OverDriveSettings) and in order to get it working again I either have to disable/enable or reboot.  Some times when I try to close out the miner window the entire computer will lock up and I have to power reset it.

Also - I enabled the logging feature and this turned off the colored output to the screen.  Anyway to get it back?   

[andrucrypt]

Is it possible to exit gracefully after a GPU has an issue?  I have a GPU that will occasionally hang/stop reporting (due to OverDriveSettings) and in order to get it working again I either have to disable/enable or reboot.  Some times when I try to close out the miner window the entire computer will lock up and I have to power reset it.

Trying different things here, but driver still prefer hang instead of release gpu.

Also - I enabled the logging feature and this turned off the colored output to the screen.  Anyway to get it back?   

No, for that some additional work needed on miner side, but that won't be in near future.

[misterkit]

Thanks.

I've also noticed that the reported hashrate varies by quite a bit.  Is this calculated based on actual results or something else?  Here's an example:
[2019-03-02 08:25:46] GPU #0: speed 10s/60s/15m 13860 13878 n/a kH/s
[2019-03-02 08:25:46] GPU #1: speed 10s/60s/15m 14865 14877 n/a kH/s
[2019-03-02 08:25:46] GPU #2: speed 10s/60s/15m 14756 14777 n/a kH/s
[2019-03-02 08:25:46] GPU #3: speed 10s/60s/15m 14929 14951 n/a kH/s
[2019-03-02 08:25:46] GPU #4: speed 10s/60s/15m 14941 14961 n/a kH/s
[2019-03-02 08:25:46] GPU #5: speed 10s/60s/15m 14059 14059 n/a kH/s
[2019-03-02 08:25:46] GPU #6: speed 10s/60s/15m 14131 14125 n/a kH/s
[2019-03-02 08:25:46] GPU #7: speed 10s/60s/15m 14138 14134 n/a kH/s
[2019-03-02 08:25:46] GPU #8: speed 10s/60s/15m 14122 14137 n/a kH/s
[2019-03-02 08:25:46] GPU #9: speed 10s/60s/15m 14948 14975 n/a kH/s
[2019-03-02 08:25:46] speed 10s/60s/15m 144754 144878 n/a kH/s max: 163640 kH/s

verse
[2019-03-02 08:58:08] GPU #0: speed 10s/60s/15m 19612 19487 15662 kH/s
[2019-03-02 08:58:08] GPU #1: speed 10s/60s/15m 21736 21649 16741 kH/s
[2019-03-02 08:58:08] GPU #2: speed 10s/60s/15m 21898 21900 16749 kH/s
[2019-03-02 08:58:08] GPU #3: speed 10s/60s/15m 22246 22181 16919 kH/s
[2019-03-02 08:58:08] GPU #4: speed 10s/60s/15m 22274 22194 16960 kH/s
[2019-03-02 08:58:08] GPU #5: speed 10s/60s/15m 20079 19917 15851 kH/s
[2019-03-02 08:58:08] GPU #6: speed 10s/60s/15m 20066 19932 15916 kH/s
[2019-03-02 08:58:08] GPU #7: speed 10s/60s/15m 20107 19966 15944 kH/s
[2019-03-02 08:58:08] GPU #8: speed 10s/60s/15m 20067 19939 15921 kH/s
[2019-03-02 08:58:08] GPU #9: speed 10s/60s/15m 22285 22163 16933 kH/s
[2019-03-02 08:58:08] speed 10s/60s/15m 210372 209331 163600 kH/s max: 212155 kH/s

verse
[2019-03-02 09:16:08] GPU #0: speed 10s/60s/15m 8943 9388 13794 kH/s
[2019-03-02 09:16:08] GPU #1: speed 10s/60s/15m 9089 9573 14789 kH/s
[2019-03-02 09:16:08] GPU #2: speed 10s/60s/15m 9007 9608 14776 kH/s
[2019-03-02 09:16:08] GPU #3: speed 10s/60s/15m 9111 9714 14887 kH/s
[2019-03-02 09:16:08] GPU #4: speed 10s/60s/15m 9109 9722 14944 kH/s
[2019-03-02 09:16:08] GPU #5: speed 10s/60s/15m 8838 9297 13870 kH/s
[2019-03-02 09:16:08] GPU #6: speed 10s/60s/15m 8910 9349 13933 kH/s
[2019-03-02 09:16:08] GPU #7: speed 10s/60s/15m 8909 9370 13953 kH/s
[2019-03-02 09:16:08] GPU #8: speed 10s/60s/15m 8872 9331 13929 kH/s
[2019-03-02 09:16:08] GPU #9: speed 10s/60s/15m 9096 9597 14859 kH/s

[andrucrypt]

Thanks.

I've also noticed that the reported hashrate varies by quite a bit.  Is this calculated based on actual results or something else?  Here's an example:

Looks like you are mining x16 family algo, or similar(bitcore, timetravel and x21s). Each of these algorithms have hashorder thing. By simply saying, more green there - higher hashrate

[misterkit]

That explains it then. Thanks

[grenwolde]

linux version v0.15.3 on linux thrwing huge errors on x16rt -- downgraded to 0.15.2 no issues.

[andrucrypt]

linux version v0.15.3 on linux thrwing huge errors on x16rt -- downgraded to 0.15.2 no issues.

What errors? What cards? Please, specify more details.

[cryptomunks]

Been using Wildrig for the last two months with X16r and X21S and I'm in love with it. Really appreciate the work you put into this.

[grenwolde]

linux version v0.15.3 on linux thrwing huge errors on x16rt -- downgraded to 0.15.2 no issues.

What errors? What cards? Please, specify more details.

sorry should have been more specific, I apologize.  Specifically, 90%+ of the shares were being rejected off of all the gpus (rx580 8gb).  No other descriptive errors were given -- when I backed off one release it was fine.  Mining Gincoin on Gos.cx.  I should mention I am mining on SMOS. 

[andrucrypt]

linux version v0.15.3 on linux thrwing huge errors on x16rt -- downgraded to 0.15.2 no issues.

What errors? What cards? Please, specify more details.

sorry should have been more specific, I apologize.  Specifically, 90%+ of the shares were being rejected off of all the gpus (rx580 8gb).  No other descriptive errors were given -- when I backed off one release it was fine.  Mining Gincoin on Gos.cx.  I should mention I am mining on SMOS. 

Errmmm, there are miners with version 0.15.3.8 on gos.cx mining GIN coin, and I don't think they are mining with that amount of rejected shares. Probably you are running with too high mem clocks(like 2000+), and that can cause a problem with modified kernels in new release.

[4ward]

Thanks.

I've also noticed that the reported hashrate varies by quite a bit.  Is this calculated based on actual results or something else?  Here's an example:

Looks like you are mining x16 family algo, or similar(bitcore, timetravel and x21s). Each of these algorithms have hashorder thing. By simply saying, more green there - higher hashrate

To my understanding, variance is and should be happening only on x16r and x16rt since the used algos vary, for others just the order changes so it should be stable

[andrucrypt]

Thanks.

I've also noticed that the reported hashrate varies by quite a bit.  Is this calculated based on actual results or something else?  Here's an example:

Looks like you are mining x16 family algo, or similar(bitcore, timetravel and x21s). Each of these algorithms have hashorder thing. By simply saying, more green there - higher hashrate

To my understanding, variance is and should be happening only on x16r and x16rt since the used algos vary, for others just the order changes so it should be stable

No, hashorder is order of different amount of hash functions(each is a separate algorithm), and if it vary - hashrate vary too. So not only x16r and x16rt have jumping hashrate.

[4ward]

Thanks.

I've also noticed that the reported hashrate varies by quite a bit.  Is this calculated based on actual results or something else?  Here's an example:

Looks like you are mining x16 family algo, or similar(bitcore, timetravel and x21s). Each of these algorithms have hashorder thing. By simply saying, more green there - higher hashrate

To my understanding, variance is and should be happening only on x16r and x16rt since the used algos vary, for others just the order changes so it should be stable

No, hashorder is order of different amount of hash functions(each is a separate algorithm), and if it vary - hashrate vary too. So not only x16r and x16rt have jumping hashrate.

Lets say it takes 10ms to calculate a slow algo and 1ms a fast one, so if you do slow first then the fast one, its 10 + 1 = 11ms
And if the order is reversed then its 1 + 10 = 11ms again... Just that you eventually do it with more algos.

x16r and x16rt the algos used are random (from a given set) so it varies, but for example x16s, its same algos but different order, so it remains stable
maybe I miss something, but this logic supports my own experience mining them

[andrucrypt]

Thanks.

I've also noticed that the reported hashrate varies by quite a bit.  Is this calculated based on actual results or something else?  Here's an example:

Looks like you are mining x16 family algo, or similar(bitcore, timetravel and x21s). Each of these algorithms have hashorder thing. By simply saying, more green there - higher hashrate

To my understanding, variance is and should be happening only on x16r and x16rt since the used algos vary, for others just the order changes so it should be stable

No, hashorder is order of different amount of hash functions(each is a separate algorithm), and if it vary - hashrate vary too. So not only x16r and x16rt have jumping hashrate.

Lets say it takes 10ms to calculate a slow algo and 1ms a fast one, so if you do slow first then the fast one, its 10 + 1 = 11ms
And if the order is reversed then its 1 + 10 = 11ms again... Just that you eventually do it with more algos.

x16r and x16rt the algos used are random (from a given set) so it varies, but for example x16s, its same algos but different order, so it remains stable
maybe I miss something, but this logic supports my own experience mining them

Who said that other algo's changing just order of constant amount hash functions? They random too. And, e.g. dedal, can even change amount of that hash functions in chain. Probably "hash order" bad term here, need to rename it somehow.