You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-------------- 20210401 19:19:44 ----------------
Mining at cfx.woolypooly.com:3094, diff: 774.09 M
GPU #3: Gigabyte NVIDIA RTX 3060 - 46.46 MH/s, 4933/4933 R:0%
Shares/min: 4.845 (Avr. 3.241)
Uptime: 1 day 1 hour 22 mins 49 secs | Algo: octopus | T-Rex v0.19.14
WD: 1 day 1 hour 22 mins 53 secs, shares: 4933/4933
20210401 19:19:49 octopus epoch: 21, block: 11504828, diff: 774.09 M
20210401 19:19:50 [ OK ] 4934/4934 - 46.47 MH/s, 43ms ... GPU #3
PS: Thank you very much for "--validate-shares" but could you make CPU share validation AFTER the miner sent the share to the pool.
The reason for this - not to increase the latency but to have information about INVL shares percent due to overclocking.
I think that changing the method from "CPU-check then send-share" to "send-share then CPU-check" is a simple thing.
May be it's a good idea to have both methods like "--validate-shares-first" and "--validate-shares-after".
The text was updated successfully, but these errors were encountered:
UPDATE:
After T-rex restart, it started to show the temp\PL\Fan on octopus.
So I think the problem is that GPU failed and T-rex watchdog did not fully restart it to restore the full functionality or something...
I mined some CFX using my 5700XTs but have not done anything with my 3060Tis or single 3070. What hashrate are you getting with your 3060 Ti? From your t-rex output, it looks like you have a 3060 AND a 3060 Ti.
Hello!
T-Rex shows Temperature, Fan, PL on Ethereum:
GPU #2: MSI NVIDIA RTX 3060 Ti - 61.45 MH/s, [T:54C, P:126W, F:50%, E:488kH/W], 398/403 R:1.24% I:0%
But NOT shows it on CFX:
-------------- 20210401 19:19:44 ----------------
Mining at cfx.woolypooly.com:3094, diff: 774.09 M
GPU #3: Gigabyte NVIDIA RTX 3060 - 46.46 MH/s, 4933/4933 R:0%
Shares/min: 4.845 (Avr. 3.241)
Uptime: 1 day 1 hour 22 mins 49 secs | Algo: octopus | T-Rex v0.19.14
WD: 1 day 1 hour 22 mins 53 secs, shares: 4933/4933
20210401 19:19:49 octopus epoch: 21, block: 11504828, diff: 774.09 M
20210401 19:19:50 [ OK ] 4934/4934 - 46.47 MH/s, 43ms ... GPU #3
PS: Thank you very much for "--validate-shares" but could you make CPU share validation AFTER the miner sent the share to the pool.
The reason for this - not to increase the latency but to have information about INVL shares percent due to overclocking.
I think that changing the method from "CPU-check then send-share" to "send-share then CPU-check" is a simple thing.
May be it's a good idea to have both methods like "--validate-shares-first" and "--validate-shares-after".
The text was updated successfully, but these errors were encountered: