Thanks for the input guys !! Final verdict : TRM rocks, NH sucks !! My Hashrate and stats are about the same as the screenshot posted about 2050 H/s with about 4% rejections !! Thx guys, bye bye NH  |
|
|
|
Hey guys, Using TRM on nicehash causes many rejected shares about 4%. Earlier used TRM on miningpoolhub and supportxmr with 0 rejects. Driver : 18.6.1 Cards : Vega 64 Config : 15+15 This is the rejection : [2019-01-07 12:36:15] Pool cryptonightv8.eu.nicehash.com share rejected. (GPU5) Error code: 2 - Job not found. (a:290 r:11) (205 ms) Is there a specific parameter to enable the nicehash support?  On the same note is the "Keepalive" parameter supported? Thx  |
|
|
|
Hi All,
Please somebody tell me how to set worker id to mine at pool.webchain.network.
Thanks!
Modify pools.txt like this: { "pools" : [ { "pool" : "pool.webchain.network:3333", "wallet" : "0xab5ab2607e801356f13978f04e4ad2909ce6c5c3", "worker" : "rig1", "password" : "x" } ] } But SRB does not work well with this algorithm. Live hashrate and hashrate pool very different is less than 3 times. LOUD miner shows much better. use srbminer 1.7.4. work perfect, but you can`t configure "worker" : "rig1", pool doesent recognize it  I cant use 1.7.4 with my 7 rigs. More duplicate shares without worker id statistic. SRB-developer cannot repair his miner. Most likely the webchain coin is too complicated for this. LOUD miner working fine. U ungrateful SOB, the Miner is awesome, if u hate it dont use it. But dont critise the dev and his works on your whims and fancies, |
|
|
|
Same problem reported here since v1.7.1 or more the vega rig became unstable. My rx580 rig have no problems with v1.7.4.
Vega 64 rig with v 1.7.4 get ramdom restarts, and i increase the mv in all gpus, lower intensity , and same problem!!
Im running a Vega Rig, but has no such issues. Which algo are you having these issues? |
|
|
|
|
Yeah Uplexa seems extremely well rounded and spot on with the cpu/gpu usage margins !!
Congrats to the devs.
|
|
|
|
OMG !! Excellent website guys, great work. Suggestion: add block time stats per coin |
|
|
|
Thank you for the new version Dok !! Restores 1mb algo speeds to their original high speeds !! For vega users : the key word being GPU_Conf "ONLY" "gpu_conf" :
[
{ "id" : 0, "intensity" : 0, "worksize" : 8, "fragments" : 1, "double_threads" : true, "old_mode" : true }
]
|
|
|
|
|
Thx for the new version.
Your thread optimisation guide for the 1mb algo is great for cpu, is it possible to tweak the gpu thread in a similar way to get higher performance on 1mb algos?
|
|
|
|
Still looking into why my 8 GB card running slow than my 4 GB cards on CN-Lite V7.
4 GB runs around 2 khs
8 GB runs about 1.7 khs
I"ve tried alot of different combos with threads, worksizes and intensity... I went all the way up to 200 intensity with dual threads work size 8... Runs slower... I tried worksize 16, slow.... Seems like I top out at intensity of 130/8/2 at 1700.
Hey dok, got any input on this one? Is this only on 172 or on older versions also? On 172 Vegas have a lower hashrate on algos with <= 1mb scratchpad, i don't know about other cards, haven't tested. I won't be fixing this because algos with <= 1mb (mox, cn-lite, dark) will soon be out of date, mox will change algo, probably others too. If you want to mine these algos, use older version of SRB. Come on man !!! Please make a try We are dependant on you. We r waiting for ur release on 1mb algo .... |
|
|
|
Hello Dok, I am having strange issues with Vega 64 and the Heavy algos. I have discovered the issue during testing and it seems like the Vega cards only hash at full potential immediately after they have been reset. If i run the benchmark again after running another algo, it drops down in hash. First run after device reset:Thread[0]: 0.0 H/s <- RX580 8GB
Thread[1]: 0.0 H/s <- RX580 8GB
Thread[2]: 1033.0 H/s <- Vega 64
Thread[3]: 1046.0 H/s <- Vega 64
Thread[4]: 973.0 H/s <- Vega 64 low clock
Thread[5]: 980.0 H/s <- Vega 64 low clock
Total: 4032.0 H/S
Thread[0]: 555.0 H/s <- RX580 8GB
Thread[1]: 555.0 H/s <- RX580 8GB
Thread[2]: 1041.0 H/s <- Vega 64
Thread[3]: 1042.0 H/s <- Vega 64
Thread[4]: 980.0 H/s <- Vega 64 low clock
Thread[5]: 979.0 H/s <- Vega 64 low clock
Total: 5152.0 H/S Thread[0]: 0.0 H/s <- RX580 8GB
Thread[1]: 0.0 H/s <- RX580 8GB
Thread[2]: 1035.0 H/s <- Vega 64
Thread[3]: 1027.0 H/s <- Vega 64
Thread[4]: 973.0 H/s <- Vega 64 low clock
Thread[5]: 970.0 H/s <- Vega 64 low clock
Total: 4005.0 H/S
Thread[0]: 555.0 H/s <- RX580 8GB
Thread[1]: 555.0 H/s <- RX580 8GB
Thread[2]: 1032.0 H/s <- Vega 64
Thread[3]: 1030.0 H/s <- Vega 64
Thread[4]: 971.0 H/s <- Vega 64 low clock
Thread[5]: 970.0 H/s <- Vega 64 low clock
Total: 5113.0 H/S It seems like no mater what algo change happens after the first run, the Heavy algos ca not reach maximum potential again till the Vega`s are reset. I have also tested "heavy_mode" : 1 and 2 but has no effect on the issue. Can confirm this behaviour on even on CN v7 algos, but --resetvega fixes these Just waiting for th CN lite code rewrites |
|
|
|
Cryptonite Lite v7 algos toke a huge hit on Vega 64... Driver on both versions : 18.6.1 SRBMiner 1.7.2: Thread[0]: 1958.0 H/s
Thread[1]: 1957.0 H/s
Thread[2]: 1891.0 H/s
Thread[3]: 1892.0 H/s
Thread[4]: 1957.0 H/s
Thread[5]: 1958.0 H/s
Thread[6]: 1959.0 H/s
Thread[7]: 1958.0 H/s
Thread[8]: 1959.0 H/s
Thread[9]: 1959.0 H/s
Thread[10]: 1964.0 H/s
Thread[11]: 1963.0 H/s
Total: 23375.0 H/S SRBMiner 1.7.1 : Thread[0]: 2265.0 H/s
Thread[1]: 2282.0 H/s
Thread[2]: 2147.0 H/s
Thread[3]: 2191.0 H/s
Thread[4]: 2334.0 H/s
Thread[5]: 2213.0 H/s
Thread[6]: 2290.0 H/s
Thread[7]: 2246.0 H/s
Thread[8]: 2297.0 H/s
Thread[9]: 2252.0 H/s
Thread[10]: 2243.0 H/s
Thread[11]: 2290.0 H/s
Total: 27050.0 H/S IDK what im doing wrong. |
|
|
|
Hey Dev, Abort was called at 767 line in file:
D:\qb\workspace\19992\src\vpg-compute-neo\runtime\os_interface\windows\wddm.cpp I have no clue !! Cards : Vega 64 Windows : 10 Driver : 18.6.1 JCE : b6 version Use directory with miner on path only with latin symbols... I have no clue what latin is? The path shown above isnt the path of miner. The miner is plain on the desktop My PC doesn't even have a "d:" |
|
|
|
Hey Dev, Abort was called at 767 line in file:
D:\qb\workspace\19992\src\vpg-compute-neo\runtime\os_interface\windows\wddm.cpp I have no clue !! Cards : Vega 64 Windows : 10 Driver : 18.6.1 JCE : b6 version |
|
|
|
Thanx for adding Mox coin pools !! |
|
|
|
Bug : Vega 64 Litev7/Mox algo Hash drop When : Pool disconnects and reconnects Tried : Different algos - LiteV7, Mox; Different pools Eg: Extract [2018-11-12 18:25:28] hashrate: GPU0: 4524 H/s [BUS:3]
[2018-11-12 18:25:28] hashrate: GPU1: 4532 H/s [BUS:6]
[2018-11-12 18:25:28] hashrate: GPU2: 4533 H/s [BUS:9]
[2018-11-12 18:25:28] hashrate: GPU3: 4340 H/s [BUS:13]
[2018-11-12 18:25:28] hashrate: GPU4: 4531 H/s [BUS:16]
[2018-11-12 18:25:28] hashrate: GPU5: 4526 H/s [BUS:19]
[2018-11-12 18:25:28] hashrate: Total: 26986 H/s
[2018-11-12 18:25:33] pool_ping: Sent keepalive message to pool
[2018-11-12 18:25:33] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"KEEPALIVED"}}
[2018-11-12 18:25:33] json_receive: Pool responded with KEEPALIVED
[2018-11-12 18:25:57] miner_result: Sending user result to pool
[2018-11-12 18:25:57] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"507345136185176","job_id":"573069932661019","nonce":"bf557b15","result":"7cc244775f372f86fd344b9147f32c7e2c3c252097c3c9b4498abf73a9090000","algo":"cn/mox"}}
[2018-11-12 18:25:57] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2018-11-12 18:25:57] miner_result: Pool accepted result 0x000009A9
[2018-11-12 18:26:28] pools: Job timeout detected, reconnecting to pool..
[2018-11-12 18:26:29] pool_ping: Couldn't send keepalive message to pool
[2018-11-12 18:26:35] Connection to pool lost. Reconnecting in 5 seconds.
[2018-11-12 18:26:41] json_send: {"id":1,"jsonrpc": "2.0","method":"login","params":{"login":"x.1600000","pass":"GKMiner","agent":"SRBMiner Cryptonight AMD GPU miner/1.7.0","rigid":"","algo":["cn/2","cn/1","cn-heavy/0","cn-heavy/xhv","cn-heavy/tube","cn/xtl","cn/msr","cn-lite/1","cn/xao","cn/rto","cn/b2n","cn/ita","cn/mkt","cn/mox","cn/0","cn/dark","cn/fest"],"algo-perf":{"cn/2": 1.0,"cn/1": 1.0,"cn-heavy/0": 1.0,"cn-heavy/xhv": 1.0,"cn-heavy/tube": 1.0,"cn/xtl": 1.0,"cn/msr": 1.0,"cn-lite/1": 1.0,"cn/xao": 1.0,"cn/rto": 1.0,"cn/b2n": 1.0,"cn/ita": 1.0,"cn/mkt": 1.0,"cn/mox": 1.0,"cn/0": 1.0,"cn/dark": 1.0,"cn/fest": 1.0},"algo-min-time": 600}}
[2018-11-12 18:26:41] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"id":"711659568315371","job":{"blob":"0707c3e7a5df0562ece3b3cddd8327146e28cd4877543c8cf6b10acf61f77df8a9755c010f03b9000000007a4a7f0f500cf97dbb6ab8c4d82a7da80f9117318f42a6b8552376d22ad1467701","job_id":"669915444171056","target":"7c0a0000","id":"711659568315371"},"status":"OK"}}
[2018-11-12 18:26:41] Connected to zzzzzz:58333
[2018-11-12 18:26:41] sock_ready: User logged in
[2018-11-12 18:26:41] pool_have_job: Pool sent a new job (ID: 669915444171056) [mox]
[2018-11-12 18:26:43] miner_result: Sending user result to pool
[2018-11-12 18:26:43] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"711659568315371","job_id":"669915444171056","nonce":"0bb4aa6a","result":"486d5d4581fcc100f5fe3fa3fb22efabfba0b867d6037150f3c98c648d090000","algo":"cn/mox"}}
[2018-11-12 18:26:43] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2018-11-12 18:26:43] miner_result: Pool accepted result 0x0000098D
[2018-11-12 18:28:34] pool_ping: Sent keepalive message to pool
[2018-11-12 18:28:34] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"KEEPALIVED"}}
[2018-11-12 18:28:34] json_receive: Pool responded with KEEPALIVED
[2018-11-12 18:29:29] hashrate: GPU0: 4253 H/s [BUS:3]
[2018-11-12 18:29:29] hashrate: GPU1: 4273 H/s [BUS:6]
[2018-11-12 18:29:29] hashrate: GPU2: 4268 H/s [BUS:9]
[2018-11-12 18:29:29] hashrate: GPU3: 4110 H/s [BUS:13]
[2018-11-12 18:29:29] hashrate: GPU4: 4257 H/s [BUS:16]
[2018-11-12 18:29:29] hashrate: GPU5: 4248 H/s [BUS:19]
[2018-11-12 18:29:29] hashrate: Total: 25409 H/s
Have multiple logs showing the same. Clocks are stable, if pool doesn't disconnect, miner is super stable |
|
|
|
V1.7.0
+ Performance boost for BitTube/Haven/Heavy/Italo algos up to ~10%, some cards gained 1% some 10%, i don't have exact numbers, you should try it out and see.
Vegas gained the most, also i hope that i fixed the Ellesmere 8Gb cards problem, not reaching max hashing speed. If you had 1k+ on some earlier versions, you should be able to reach it now again but you MUST set fragments to 0 if you are setting it by hand, otherwise it probably won't reach max speeds.
And no fee increase because of the extra performance, it stays at ~0.85%
+ Some small optimisation gained around +10hs on my test Vega56 on V8 algo
Spot on: Vega 64 : | Algo | 1.6.9 | 1.7.0 | | Heavy | 1550 | 1685 | | V8 | 2018 | 2035 |
Almost same power consumption Thx doc !~! |
|
|
|
Last night noticed on the pool side gap in hash for period for more than 1 hour, then in the log file found gap that correspond to that drop in hashrate on the pool. Why this gap of more than 70 minutes? Can I setup that miner closes when gpu chrash is detected so my own script can take care of it? [2018-11-07 00:47:33] watchdog: GPU crash detected, miner will try to restart
[2018-11-07 00:47:33] Restarting miner process
[2018-11-07 00:47:34] Miner version: 1.6.8
[2018-11-07 00:47:34] Windows version: 10.0 build 15063
[2018-11-07 00:47:34] Video driver version: 24.20.11016.4
[2018-11-07 00:50:47] AMD Platform ID: 1
[2018-11-07 00:50:47] AMD platform FOUND
[2018-11-07 00:50:47] Found 5 AMD devices
[2018-11-07 00:50:47] CPU AES-NI: TRUE
[2018-11-07 00:50:47] GPU0: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 4]
[2018-11-07 00:50:47] GPU1: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 16]
[2018-11-07 00:50:47] GPU2: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 13]
[2018-11-07 00:50:47] GPU3: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 10]
[2018-11-07 00:50:47] GPU4: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 7]
[2018-11-07 00:50:47] ADL is enabled
[2018-11-07 00:50:47] Cryptonight Fast mode enabled
[2018-11-07 00:50:47] Starting init of mining threads
[2018-11-07 00:50:47] Heating up system, please wait...
[2018-11-07 00:50:47] Created OCL context
[2018-11-07 00:50:47] Created OCL command queue for DeviceID 0 (Thread 0)
[2018-11-07 00:50:47] Created OCL input buffer for DeviceID 0 (Thread 0)
[2018-11-07 00:50:47] Created OCL output buffer for DeviceID 0 (Thread 0)
[2018-11-07 00:50:47] Loading kernel for DEVICE BUS ID 4 ...
[2018-11-07 00:50:47] Created OCL command queue for DeviceID 0 (Thread 1)
[2018-11-07 00:50:47] Created OCL input buffer for DeviceID 0 (Thread 1)
[2018-11-07 00:50:47] Created OCL output buffer for DeviceID 0 (Thread 1)
[2018-11-07 00:50:47] Loading kernel for DEVICE BUS ID 4 ...
[2018-11-07 00:50:47] Created OCL command queue for DeviceID 1 (Thread 2)
[2018-11-07 00:50:47] Created OCL input buffer for DeviceID 1 (Thread 2)
[2018-11-07 00:50:47] Created OCL output buffer for DeviceID 1 (Thread 2)
[2018-11-07 00:50:47] Loading kernel for DEVICE BUS ID 16 ...
[2018-11-07 00:50:47] Created OCL command queue for DeviceID 1 (Thread 3)
[2018-11-07 00:50:47] Created OCL input buffer for DeviceID 1 (Thread 3)
[2018-11-07 00:50:47] Created OCL output buffer for DeviceID 1 (Thread 3)
[2018-11-07 00:50:47] Loading kernel for DEVICE BUS ID 16 ...
[2018-11-07 00:50:55] Miner version: 1.6.8
[2018-11-07 00:50:55] Windows version: 10.0 build 15063
[2018-11-07 00:50:55] Video driver version: 24.20.11016.4
[2018-11-07 02:03:04] AMD Platform ID: 1
[2018-11-07 02:03:04] AMD platform FOUND
[2018-11-07 02:03:04] Found 5 AMD devices
[2018-11-07 02:03:04] CPU AES-NI: TRUE
[2018-11-07 02:03:04] GPU0: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 4]
[2018-11-07 02:03:04] GPU1: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 16]
[2018-11-07 02:03:04] GPU2: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 13]
[2018-11-07 02:03:04] GPU3: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 10]
[2018-11-07 02:03:04] GPU4: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 7]
[2018-11-07 02:03:04] ADL is enabled
[2018-11-07 02:03:04] Cryptonight Fast mode enabled
[2018-11-07 02:03:04] Starting init of mining threads
[2018-11-07 02:03:04] Heating up system, please wait...
[2018-11-07 02:03:04] Created OCL context
[2018-11-07 02:03:04] Created OCL command queue for DeviceID 0 (Thread 0)
[2018-11-07 02:03:04] Created OCL input buffer for DeviceID 0 (Thread 0)
Adding "--disablegpuwatchdog (disable gpu crash detection watchdog)" to start.bat allows u to control crash responses. |
|
|
|
Waitting for it, hope the new graphs support 24h view instead of 8hr view !! |
|
|
|
|
Show Posts
