activatorwmw
Newbie
Offline
Activity: 9
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
April 27, 2018, 07:56:25 PM |
|
Hi all! First of all, sorry for my bad English.
I have a problem. my rig on win10, msi afterburner, zm 0.6, 8 nvidia GPU, at config i set temp limit 67. While i use remote desktop (teamviewer) all works well, temp limit reduce intensity at 67 and increase it back well. But if i disconnected from remote desktop intensity not increasing after reducing by temp limit and working at low hashrate.When i just reconnect to remote desktop intensity increasing back. Who can help me? p.s. the same situation at my 2 rig with 5 nvidia GPU.
Are you sure the performance drop is related to temperature controller? i.e. does it really only happen with temp-target enabled? Pls pm me your logfile, I'll check if there is something unusual. All night without temp limit. no low hashrate.
|
|
|
|
dstm (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
April 27, 2018, 08:21:01 PM |
|
Hi all! First of all, sorry for my bad English.
I have a problem. my rig on win10, msi afterburner, zm 0.6, 8 nvidia GPU, at config i set temp limit 67. While i use remote desktop (teamviewer) all works well, temp limit reduce intensity at 67 and increase it back well. But if i disconnected from remote desktop intensity not increasing after reducing by temp limit and working at low hashrate.When i just reconnect to remote desktop intensity increasing back. Who can help me? p.s. the same situation at my 2 rig with 5 nvidia GPU.
Are you sure the performance drop is related to temperature controller? i.e. does it really only happen with temp-target enabled? Pls pm me your logfile, I'll check if there is something unusual. All night without temp limit. no low hashrate. Thx for doing the test - I'll go trough the code of temperature-controller this weekend.
|
|
|
|
Andrey09
Newbie
Offline
Activity: 176
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
April 28, 2018, 10:33:02 AM |
|
I guess it because gpu have algorithms to reduce the performance of the temperature increase. (indeed temp lower <70 C). I mean gpu 50 C will show more sols then with temp 60C or 70C. (on same frequency)
I also noticed the regularity that the lower the temperature, the greater the productivity. (in sols in DSTM)
|
|
|
|
Borsiy
Newbie
Offline
Activity: 13
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
April 28, 2018, 05:42:48 PM |
|
Hi all! First of all, sorry for my bad English.
I have a problem. my rig on win10, msi afterburner, zm 0.6, 8 nvidia GPU, at config i set temp limit 67. While i use remote desktop (teamviewer) all works well, temp limit reduce intensity at 67 and increase it back well. But if i disconnected from remote desktop intensity not increasing after reducing by temp limit and working at low hashrate.When i just reconnect to remote desktop intensity increasing back. Who can help me? p.s. the same situation at my 2 rig with 5 nvidia GPU.
Are you sure the performance drop is related to temperature controller? i.e. does it really only happen with temp-target enabled? Pls pm me your logfile, I'll check if there is something unusual. I have the same problem on win7, zm 0.6, temp limit 70°, 100% fan. When GPU start temperature control AND i don't watch it via Teamviewer, GPU usage drops and don't restore until i join TV again. Here is log of GPU usage drops on temp° controller and restores when i joined TV. 2018-04-28 18:34:04| GPU0 66C Sol/s: 525.0 Sol/W: 2.71 Avg: 534.6 I/s: 287.1 Sh: 0.94 1.00 94 2018-04-28 18:34:05| GPU1 60C Sol/s: 501.7 Sol/W: 3.33 Avg: 497.0 I/s: 266.2 Sh: 1.43 1.00 93 2018-04-28 18:34:05| GPU2 69C Sol/s: 526.3 Sol/W: 2.74 Avg: 536.0 I/s: 287.3 Sh: 0.98 1.00 78 2018-04-28 18:34:08| GPU3 66C Sol/s: 538.8 Sol/W: 2.74 Avg: 536.1 I/s: 287.1 Sh: 1.56 1.00 78 + 2018-04-28 18:34:10| GPU4 64C Sol/s: 475.5 Sol/W: 3.68 Avg: 487.3 I/s: 260.4 Sh: 0.85 1.00 78 ++ 2018-04-28 18:34:10| GPU5 69C Sol/s: 544.5 Sol/W: 2.67 Avg: 536.1 I/s: 287.6 Sh: 1.07 1.00 93 + 2018-04-28 18:34:11| ========== Sol/s: 3111.9 Sol/W: 2.98 Avg: 3127.1 I/s: 1675.7 Sh: 6.83 1.00 85 2018-04-28 18:34:24| GPU0 66C Sol/s: 535.6 Sol/W: 2.71 Avg: 534.7 I/s: 287.1 Sh: 0.92 1.00 94 2018-04-28 18:34:24|# GPU2 reached temperature target 70C 2018-04-28 18:34:24|# GPU2 enabling temperature controller 2018-04-28 18:34:25| GPU1 60C Sol/s: 501.4 Sol/W: 3.33 Avg: 497.1 I/s: 266.2 Sh: 1.41 1.00 93 2018-04-28 18:34:25| GPU2 64C Sol/s: 520.4 Sol/W: 2.74 Avg: 535.8 I/s: 276.6 Sh: 0.97 1.00 78 2018-04-28 18:34:28| GPU3 67C Sol/s: 536.9 Sol/W: 2.74 Avg: 536.1 I/s: 287.1 Sh: 1.54 1.00 78 2018-04-28 18:34:30| GPU4 64C Sol/s: 490.3 Sol/W: 3.68 Avg: 487.4 I/s: 260.4 Sh: 0.84 1.00 78 2018-04-28 18:34:31| GPU5 69C Sol/s: 530.4 Sol/W: 2.67 Avg: 536.0 I/s: 287.6 Sh: 1.06 1.00 93 2018-04-28 18:34:31| ========== Sol/s: 3114.9 Sol/W: 2.98 Avg: 3127.0 I/s: 1665.0 Sh: 6.73 1.00 85 2018-04-28 18:34:44|> GPU0 66C Sol/s: 533.8 Sol/W: 2.71 Avg: 534.6 I/s: 286.9 Sh: 0.91 1.00 94 2018-04-28 18:34:45|> GPU1 60C Sol/s: 494.6 Sol/W: 3.33 Avg: 497.0 I/s: 266.4 Sh: 1.39 1.00 93 2018-04-28 18:34:46|> GPU2 49C Sol/s: 120.0 Sol/W: 2.74 Avg: 529.7 I/s: 64.1 Sh: 0.95 1.00 78 2018-04-28 18:34:48|> GPU3 67C Sol/s: 536.2 Sol/W: 2.74 Avg: 536.1 I/s: 287.1 Sh: 1.52 1.00 78 2018-04-28 18:34:51|> GPU4 64C Sol/s: 485.2 Sol/W: 3.68 Avg: 487.3 I/s: 260.4 Sh: 0.82 1.00 78 2018-04-28 18:34:51|> GPU5 69C Sol/s: 536.8 Sol/W: 2.67 Avg: 536.0 I/s: 287.3 Sh: 1.08 1.00 78 + 2018-04-28 18:34:51| ========== Sol/s: 2706.5 Sol/W: 2.98 Avg: 3120.9 I/s: 1452.2 Sh: 6.68 1.00 83 2018-04-28 18:35:04|> GPU0 66C Sol/s: 535.0 Sol/W: 2.71 Avg: 534.7 I/s: 287.1 Sh: 0.94 1.00 78 + 2018-04-28 18:35:05|> GPU1 60C Sol/s: 498.8 Sol/W: 3.33 Avg: 497.0 I/s: 266.0 Sh: 1.37 1.00 93 2018-04-28 18:35:06|> GPU2 45C Sol/s: 120.2 Sol/W: 2.73 Avg: 523.9 I/s: 64.0 Sh: 0.98 1.00 78 + 2018-04-28 18:35:08|> GPU3 67C Sol/s: 537.0 Sol/W: 2.74 Avg: 536.1 I/s: 287.3 Sh: 1.50 1.00 78 2018-04-28 18:35:11|> GPU4 64C Sol/s: 495.4 Sol/W: 3.69 Avg: 487.5 I/s: 260.4 Sh: 0.81 1.00 78 2018-04-28 18:35:11|> GPU5 69C Sol/s: 536.2 Sol/W: 2.67 Avg: 536.0 I/s: 287.6 Sh: 1.07 1.00 78 2018-04-28 18:35:11| ========== Sol/s: 2722.7 Sol/W: 2.98 Avg: 3115.2 I/s: 1452.4 Sh: 6.67 1.00 80
2018-04-28 21:06:36|> GPU0 65C Sol/s: 534.2 Sol/W: 2.72 Avg: 535.5 I/s: 287.1 Sh: 1.27 1.00 93 2018-04-28 21:06:36|> GPU4 64C Sol/s: 501.7 Sol/W: 3.64 Avg: 488.6 I/s: 262.4 Sh: 1.17 1.00 78 + 2018-04-28 21:06:37|> GPU3 63C Sol/s: 532.1 Sol/W: 2.75 Avg: 535.9 I/s: 286.9 Sh: 1.24 1.00 78 2018-04-28 21:06:40| GPU2 38C Sol/s: 118.8 Sol/W: 2.26 Avg: 174.5 I/s: 64.0 Sh: 0.36 1.00 78 2018-04-28 21:06:40| GPU1 59C Sol/s: 496.1 Sol/W: 3.32 Avg: 496.9 I/s: 266.2 Sh: 1.23 1.00 78 2018-04-28 21:06:50| GPU5 41C Sol/s: 119.1 Sol/W: 2.37 Avg: 254.5 I/s: 64.0 Sh: 0.54 1.00 78 2018-04-28 21:06:50| ========== Sol/s: 2302.0 Sol/W: 2.84 Avg: 2485.9 I/s: 1230.4 Sh: 5.81 1.00 80 2018-04-28 21:06:56| GPU0 65C Sol/s: 539.4 Sol/W: 2.72 Avg: 535.5 I/s: 286.9 Sh: 1.27 1.00 93 2018-04-28 21:06:56| GPU4 64C Sol/s: 486.7 Sol/W: 3.64 Avg: 488.6 I/s: 262.4 Sh: 1.17 1.00 93 + 2018-04-28 21:06:57| GPU3 64C Sol/s: 547.5 Sol/W: 2.75 Avg: 536.0 I/s: 286.9 Sh: 1.24 1.00 78 2018-04-28 21:07:00| GPU2 38C Sol/s: 122.8 Sol/W: 2.26 Avg: 174.4 I/s: 64.0 Sh: 0.37 1.00 78 ++ 2018-04-28 21:07:00| GPU1 59C Sol/s: 494.8 Sol/W: 3.32 Avg: 496.8 I/s: 266.2 Sh: 1.24 1.00 85 ++* 2018-04-28 21:07:10| GPU5 50C Sol/s: 211.3 Sol/W: 2.37 Avg: 254.4 I/s: 111.8 Sh: 0.55 1.00 78 + 2018-04-28 21:07:10| ========== Sol/s: 2402.5 Sol/W: 2.84 Avg: 2485.8 I/s: 1278.1 Sh: 5.84 1.00 84 2018-04-28 21:07:16| GPU0 65C Sol/s: 539.9 Sol/W: 2.72 Avg: 535.5 I/s: 285.3 Sh: 1.27 1.00 93 2018-04-28 21:07:16| GPU4 64C Sol/s: 480.4 Sol/W: 3.64 Avg: 488.6 I/s: 261.9 Sh: 1.17 1.00 93 2018-04-28 21:07:17| GPU3 64C Sol/s: 533.1 Sol/W: 2.75 Avg: 536.0 I/s: 285.5 Sh: 1.24 1.00 78 2018-04-28 21:07:20|> GPU2 57C Sol/s: 406.8 Sol/W: 2.26 Avg: 174.8 I/s: 220.4 Sh: 0.37 1.00 78 2018-04-28 21:07:20|> GPU1 59C Sol/s: 499.1 Sol/W: 3.32 Avg: 496.9 I/s: 265.6 Sh: 1.24 1.00 85 2018-04-28 21:07:30|> GPU5 57C Sol/s: 532.7 Sol/W: 2.37 Avg: 255.0 I/s: 288.2 Sh: 0.55 1.00 79 + 2018-04-28 21:07:30| ========== Sol/s: 2992.1 Sol/W: 2.84 Avg: 2486.7 I/s: 1606.9 Sh: 5.83 1.00 84 2018-04-28 21:07:36|> GPU0 64C Sol/s: 524.3 Sol/W: 2.72 Avg: 535.5 I/s: 284.9 Sh: 1.27 1.00 93 2018-04-28 21:07:36|> GPU4 64C Sol/s: 496.0 Sol/W: 3.64 Avg: 488.6 I/s: 261.8 Sh: 1.17 1.00 93 2018-04-28 21:07:38|> GPU3 64C Sol/s: 538.1 Sol/W: 2.75 Avg: 536.0 I/s: 285.6 Sh: 1.23 1.00 78 2018-04-28 21:07:40| GPU2 62C Sol/s: 528.3 Sol/W: 2.27 Avg: 175.5 I/s: 286.4 Sh: 0.38 1.00 80 ++ 2018-04-28 21:07:40| GPU1 59C Sol/s: 488.7 Sol/W: 3.32 Avg: 496.8 I/s: 262.7 Sh: 1.24 1.00 85 2018-04-28 21:07:50| GPU5 60C Sol/s: 533.1 Sol/W: 2.37 Avg: 255.5 I/s: 283.5 Sh: 0.55 1.00 79 2018-04-28 21:07:50| ========== Sol/s: 3108.5 Sol/W: 2.84 Avg: 2487.9 I/s: 1664.9 Sh: 5.83 1.00 84
And here is typical GPU usage and temp graphic: https://preview.ibb.co/iVix1x/screenshot_22.pngOne more question, dstm. Could you add temperature limit option for GPU emergency shutdown (like in Claymore)? The reason for having such option is that your temperature controller works best with 100% fan setting, but it destroy fan very quickly. So it's sometimes good to have PID on fan and hard temp° limit to be sure GPU will turn off if exceed the limit.
|
|
|
|
TheMrJ
Newbie
Offline
Activity: 62
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
April 29, 2018, 02:12:13 PM |
|
Is there a function in dstm to restart the computer if the mining speed falls under a select value? In claymore you can set up that the miner restarts after 5min if the hash falls below the chosen value.
How can I set up this function in dstm, in the readme file they are no comment about this..
|
|
|
|
timbereagle
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
April 29, 2018, 03:24:48 PM |
|
I was away from mining for some time.
I know DSTM is %2 fee whereas EWBF is %1.
Can someone tell me how much DSTM is faster for
GTX 1060 1070 1080ti?
In December DSTM was faster %1.5 %2 and almost same result with EWBF because of fee difference.
|
|
|
|
blazeaglory
Newbie
Offline
Activity: 21
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
April 29, 2018, 04:42:45 PM |
|
Im getting roughly 500sol/s NON OC with my GIGABYTE windforce 8gb 1080
How are so many people getting great (550 or more sol/s) with their 1070ti?
|
|
|
|
blazeaglory
Newbie
Offline
Activity: 21
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
April 29, 2018, 04:52:42 PM |
|
I was away from mining for some time.
I know DSTM is %2 fee whereas EWBF is %1.
Can someone tell me how much DSTM is faster for
GTX 1060 1070 1080ti?
In December DSTM was faster %1.5 %2 and almost same result with EWBF because of fee difference.
I dont know about others, I can only speak for myself but last year or so Ive seen better and faster results using DSTM mining Zcash on nanopool. I see lower speeds and weird devfee with EFWB in last month or so. But then again, it does seem to run extremely well on suprnova compared to nanopool.
|
|
|
|
yonargi
Newbie
Offline
Activity: 6
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
April 29, 2018, 06:34:16 PM |
|
A virus kicked my miner off-line and I am trying to set it up again. I get to the "edit" page, put in my data, save, but it doesn't take off, which it did when I first set it up. What am I doing wrong? May I turn on the firewall to run with it? If so, what should I put in the firewall as a exclusion?
|
|
|
|
activatorwmw
Newbie
Offline
Activity: 9
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
April 29, 2018, 09:02:15 PM Last edit: April 30, 2018, 04:08:22 AM by activatorwmw |
|
I was away from mining for some time.
I know DSTM is %2 fee whereas EWBF is %1.
Can someone tell me how much DSTM is faster for
GTX 1060 1070 1080ti?
In December DSTM was faster %1.5 %2 and almost same result with EWBF because of fee difference.
You can see it here https://bitcointalk.org/index.php?topic=2021765.msg35677463#msg35677463and for 1060 6gb 2018-04-30 16:04:59| ========== Sol/s: 1333.7 Sol/W: 3.30 Avg: 1329.9 I/s: 712.3 Sh: 4.91 0.99 184 2018-04-30 16:05:05| GPU1 63C Sol/s: 329.2 Sol/W: 3.28 Avg: 332.2 I/s: 177.9 Sh: 1.23 0.98 178 2018-04-30 16:05:06| GPU2 64C Sol/s: 327.1 Sol/W: 3.27 Avg: 331.4 I/s: 177.4 Sh: 1.24 0.98 178 2018-04-30 16:05:10| GPU0 58C Sol/s: 331.2 Sol/W: 3.28 Avg: 332.5 I/s: 178.1 Sh: 1.20 0.99 201 2018-04-30 16:05:19|> GPU3 66C Sol/s: 338.1 Sol/W: 3.37 Avg: 333.7 I/s: 179.2 Sh: 1.24 1.00 179 2018-04-30 16:05:19| ========== Sol/s: 1325.5 Sol/W: 3.30 Avg: 1329.9 I/s: 712.7 Sh: 4.91 0.99 184 2018-04-30 16:05:26|> GPU1 63C Sol/s: 331.5 Sol/W: 3.28 Avg: 332.2 I/s: 177.7 Sh: 1.23 0.98 178 + 2018-04-30 16:05:26|> GPU2 64C Sol/s: 323.4 Sol/W: 3.27 Avg: 331.4 I/s: 177.4 Sh: 1.24 0.98 178 2018-04-30 16:05:30|> GPU0 58C Sol/s: 335.7 Sol/W: 3.28 Avg: 332.5 I/s: 178.2 Sh: 1.20 0.99 201 2018-04-30 16:05:39| GPU3 66C Sol/s: 337.0 Sol/W: 3.37 Avg: 333.7 I/s: 179.2 Sh: 1.24 1.00 179 2018-04-30 16:05:39| ========== Sol/s: 1327.7 Sol/W: 3.30 Avg: 1329.9 I/s: 712.6 Sh: 4.91 0.99 184
|
|
|
|
timbereagle
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
April 30, 2018, 05:02:32 AM |
|
I was away from mining for some time.
I know DSTM is %2 fee whereas EWBF is %1.
Can someone tell me how much DSTM is faster for
GTX 1060 1070 1080ti?
In December DSTM was faster %1.5 %2 and almost same result with EWBF because of fee difference.
You can see it here https://bitcointalk.org/index.php?topic=2021765.msg35677463#msg35677463and for 1060 6gb 2018-04-30 16:04:59| ========== Sol/s: 1333.7 Sol/W: 3.30 Avg: 1329.9 I/s: 712.3 Sh: 4.91 0.99 184 2018-04-30 16:05:05| GPU1 63C Sol/s: 329.2 Sol/W: 3.28 Avg: 332.2 I/s: 177.9 Sh: 1.23 0.98 178 2018-04-30 16:05:06| GPU2 64C Sol/s: 327.1 Sol/W: 3.27 Avg: 331.4 I/s: 177.4 Sh: 1.24 0.98 178 2018-04-30 16:05:10| GPU0 58C Sol/s: 331.2 Sol/W: 3.28 Avg: 332.5 I/s: 178.1 Sh: 1.20 0.99 201 2018-04-30 16:05:19|> GPU3 66C Sol/s: 338.1 Sol/W: 3.37 Avg: 333.7 I/s: 179.2 Sh: 1.24 1.00 179 2018-04-30 16:05:19| ========== Sol/s: 1325.5 Sol/W: 3.30 Avg: 1329.9 I/s: 712.7 Sh: 4.91 0.99 184 2018-04-30 16:05:26|> GPU1 63C Sol/s: 331.5 Sol/W: 3.28 Avg: 332.2 I/s: 177.7 Sh: 1.23 0.98 178 + 2018-04-30 16:05:26|> GPU2 64C Sol/s: 323.4 Sol/W: 3.27 Avg: 331.4 I/s: 177.4 Sh: 1.24 0.98 178 2018-04-30 16:05:30|> GPU0 58C Sol/s: 335.7 Sol/W: 3.28 Avg: 332.5 I/s: 178.2 Sh: 1.20 0.99 201 2018-04-30 16:05:39| GPU3 66C Sol/s: 337.0 Sol/W: 3.37 Avg: 333.7 I/s: 179.2 Sh: 1.24 1.00 179 2018-04-30 16:05:39| ========== Sol/s: 1327.7 Sol/W: 3.30 Avg: 1329.9 I/s: 712.6 Sh: 4.91 0.99 184 Wow, thank you. For GTX 1060 and 1070 speed gap is almost %6. For GTX 1080ti around %1-2. So I would use DSTM's miner even it has bigger fee.
|
|
|
|
Mark899
Newbie
Offline
Activity: 19
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
April 30, 2018, 01:22:44 PM Last edit: April 30, 2018, 02:46:10 PM by Mark899 |
|
I can't seem to figure out how to disable a gpu in DSTM. https://i.imgur.com/hfGlRKV.pngWhen I use --dev 0 2 3 in the .CFG file, the miner shows an error and wont start. I have no clue what I'm doing wrong. I assume I'm putting in the wrong place, or there's another command I'm suppose to put in there. EWBF I just remove the number in my cuda device, and others I can simply type in the number while the miner is running to turn them off individually. Any help would greatly be appreciated!
|
|
|
|
chaostic
Newbie
Offline
Activity: 22
Merit: 2
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
April 30, 2018, 02:52:23 PM |
|
I can't seem to figure out how to disable a gpu in DSTM. https://i.imgur.com/hfGlRKV.pngWhen I use --dev 0 2 3 in the .CFG file, the miner shows an error and wont start. I have no clue what I'm doing wrong. I assume I'm putting in the wrong place, or there's another command I'm suppose to put in there. EWBF I just remove the number in my cuda device, and others I can simply type in the number while the miner is running to turn them off individually. Any help would greatly be appreciated! Make a batch file, I use --telemetry and --dev 0 1 2 3 5, try making you're own config file a simple .bat
|
|
|
|
buck54321
Newbie
Offline
Activity: 6
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 01, 2018, 01:28:57 AM |
|
I would like to incorporate your miner into some software, but I really need to know immediately when shares are accepted. Any plans to implement a verbosity or similar?
|
|
|
|
msklogix
Newbie
Offline
Activity: 3
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/question.gif) |
May 02, 2018, 01:25:39 AM Last edit: May 02, 2018, 02:39:55 AM by msklogix |
|
Hello DSTM, I don't mind paying 2% dev fee, however, I noticed the v0.6 is currently submitting more dev shares than it should. could you explain in detail how actually are you calculating it? well in a very simple calculation 2% could be 2 shares in 100 accepted shares? isn't it that simple? ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) Would appreciate your quick reply. Thanks,
|
|
|
|
nUm81
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 02, 2018, 10:23:06 AM |
|
Its not really that simple, with the variable difficulty on pools, the pool that the dev mines to will have a different difficulty then the pool that you are mining too.
|
|
|
|
korenchkin
Newbie
Offline
Activity: 11
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 02, 2018, 11:10:16 AM |
|
Hello DSTM, I don't mind paying 2% dev fee, however, I noticed the v0.6 is currently submitting more dev shares than it should. could you explain in detail how actually are you calculating it? well in a very simple calculation 2% could be 2 shares in 100 accepted shares? isn't it that simple? ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) Would appreciate your quick reply. Thanks, i believe the only way to do this is to dedicate 2% of time,but he probably needs lower difficulty so he gets some shares on the limited time(because only shares count on pool,so this may look like he mines more for himself),but that's just a guess
|
|
|
|
dstm (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 02, 2018, 02:12:59 PM |
|
Hi all! First of all, sorry for my bad English.
I have a problem. my rig on win10, msi afterburner, zm 0.6, 8 nvidia GPU, at config i set temp limit 67. While i use remote desktop (teamviewer) all works well, temp limit reduce intensity at 67 and increase it back well. But if i disconnected from remote desktop intensity not increasing after reducing by temp limit and working at low hashrate.When i just reconnect to remote desktop intensity increasing back. Who can help me? p.s. the same situation at my 2 rig with 5 nvidia GPU.
Are you sure the performance drop is related to temperature controller? i.e. does it really only happen with temp-target enabled? Pls pm me your logfile, I'll check if there is something unusual. I have the same problem on win7, zm 0.6, temp limit 70°, 100% fan. When GPU start temperature control AND i don't watch it via Teamviewer, GPU usage drops and don't restore until i join TV again. Here is log of GPU usage drops on temp° controller and restores when i joined TV. 2018-04-28 18:34:04| GPU0 66C Sol/s: 525.0 Sol/W: 2.71 Avg: 534.6 I/s: 287.1 Sh: 0.94 1.00 94 2018-04-28 18:34:05| GPU1 60C Sol/s: 501.7 Sol/W: 3.33 Avg: 497.0 I/s: 266.2 Sh: 1.43 1.00 93 2018-04-28 18:34:05| GPU2 69C Sol/s: 526.3 Sol/W: 2.74 Avg: 536.0 I/s: 287.3 Sh: 0.98 1.00 78 2018-04-28 18:34:08| GPU3 66C Sol/s: 538.8 Sol/W: 2.74 Avg: 536.1 I/s: 287.1 Sh: 1.56 1.00 78 + 2018-04-28 18:34:10| GPU4 64C Sol/s: 475.5 Sol/W: 3.68 Avg: 487.3 I/s: 260.4 Sh: 0.85 1.00 78 ++ 2018-04-28 18:34:10| GPU5 69C Sol/s: 544.5 Sol/W: 2.67 Avg: 536.1 I/s: 287.6 Sh: 1.07 1.00 93 + 2018-04-28 18:34:11| ========== Sol/s: 3111.9 Sol/W: 2.98 Avg: 3127.1 I/s: 1675.7 Sh: 6.83 1.00 85 2018-04-28 18:34:24| GPU0 66C Sol/s: 535.6 Sol/W: 2.71 Avg: 534.7 I/s: 287.1 Sh: 0.92 1.00 94 2018-04-28 18:34:24|# GPU2 reached temperature target 70C 2018-04-28 18:34:24|# GPU2 enabling temperature controller 2018-04-28 18:34:25| GPU1 60C Sol/s: 501.4 Sol/W: 3.33 Avg: 497.1 I/s: 266.2 Sh: 1.41 1.00 93 2018-04-28 18:34:25| GPU2 64C Sol/s: 520.4 Sol/W: 2.74 Avg: 535.8 I/s: 276.6 Sh: 0.97 1.00 78 2018-04-28 18:34:28| GPU3 67C Sol/s: 536.9 Sol/W: 2.74 Avg: 536.1 I/s: 287.1 Sh: 1.54 1.00 78 2018-04-28 18:34:30| GPU4 64C Sol/s: 490.3 Sol/W: 3.68 Avg: 487.4 I/s: 260.4 Sh: 0.84 1.00 78 2018-04-28 18:34:31| GPU5 69C Sol/s: 530.4 Sol/W: 2.67 Avg: 536.0 I/s: 287.6 Sh: 1.06 1.00 93 2018-04-28 18:34:31| ========== Sol/s: 3114.9 Sol/W: 2.98 Avg: 3127.0 I/s: 1665.0 Sh: 6.73 1.00 85 2018-04-28 18:34:44|> GPU0 66C Sol/s: 533.8 Sol/W: 2.71 Avg: 534.6 I/s: 286.9 Sh: 0.91 1.00 94 2018-04-28 18:34:45|> GPU1 60C Sol/s: 494.6 Sol/W: 3.33 Avg: 497.0 I/s: 266.4 Sh: 1.39 1.00 93 2018-04-28 18:34:46|> GPU2 49C Sol/s: 120.0 Sol/W: 2.74 Avg: 529.7 I/s: 64.1 Sh: 0.95 1.00 78 2018-04-28 18:34:48|> GPU3 67C Sol/s: 536.2 Sol/W: 2.74 Avg: 536.1 I/s: 287.1 Sh: 1.52 1.00 78 2018-04-28 18:34:51|> GPU4 64C Sol/s: 485.2 Sol/W: 3.68 Avg: 487.3 I/s: 260.4 Sh: 0.82 1.00 78 2018-04-28 18:34:51|> GPU5 69C Sol/s: 536.8 Sol/W: 2.67 Avg: 536.0 I/s: 287.3 Sh: 1.08 1.00 78 + 2018-04-28 18:34:51| ========== Sol/s: 2706.5 Sol/W: 2.98 Avg: 3120.9 I/s: 1452.2 Sh: 6.68 1.00 83 2018-04-28 18:35:04|> GPU0 66C Sol/s: 535.0 Sol/W: 2.71 Avg: 534.7 I/s: 287.1 Sh: 0.94 1.00 78 + 2018-04-28 18:35:05|> GPU1 60C Sol/s: 498.8 Sol/W: 3.33 Avg: 497.0 I/s: 266.0 Sh: 1.37 1.00 93 2018-04-28 18:35:06|> GPU2 45C Sol/s: 120.2 Sol/W: 2.73 Avg: 523.9 I/s: 64.0 Sh: 0.98 1.00 78 + 2018-04-28 18:35:08|> GPU3 67C Sol/s: 537.0 Sol/W: 2.74 Avg: 536.1 I/s: 287.3 Sh: 1.50 1.00 78 2018-04-28 18:35:11|> GPU4 64C Sol/s: 495.4 Sol/W: 3.69 Avg: 487.5 I/s: 260.4 Sh: 0.81 1.00 78 2018-04-28 18:35:11|> GPU5 69C Sol/s: 536.2 Sol/W: 2.67 Avg: 536.0 I/s: 287.6 Sh: 1.07 1.00 78 2018-04-28 18:35:11| ========== Sol/s: 2722.7 Sol/W: 2.98 Avg: 3115.2 I/s: 1452.4 Sh: 6.67 1.00 80
2018-04-28 21:06:36|> GPU0 65C Sol/s: 534.2 Sol/W: 2.72 Avg: 535.5 I/s: 287.1 Sh: 1.27 1.00 93 2018-04-28 21:06:36|> GPU4 64C Sol/s: 501.7 Sol/W: 3.64 Avg: 488.6 I/s: 262.4 Sh: 1.17 1.00 78 + 2018-04-28 21:06:37|> GPU3 63C Sol/s: 532.1 Sol/W: 2.75 Avg: 535.9 I/s: 286.9 Sh: 1.24 1.00 78 2018-04-28 21:06:40| GPU2 38C Sol/s: 118.8 Sol/W: 2.26 Avg: 174.5 I/s: 64.0 Sh: 0.36 1.00 78 2018-04-28 21:06:40| GPU1 59C Sol/s: 496.1 Sol/W: 3.32 Avg: 496.9 I/s: 266.2 Sh: 1.23 1.00 78 2018-04-28 21:06:50| GPU5 41C Sol/s: 119.1 Sol/W: 2.37 Avg: 254.5 I/s: 64.0 Sh: 0.54 1.00 78 2018-04-28 21:06:50| ========== Sol/s: 2302.0 Sol/W: 2.84 Avg: 2485.9 I/s: 1230.4 Sh: 5.81 1.00 80 2018-04-28 21:06:56| GPU0 65C Sol/s: 539.4 Sol/W: 2.72 Avg: 535.5 I/s: 286.9 Sh: 1.27 1.00 93 2018-04-28 21:06:56| GPU4 64C Sol/s: 486.7 Sol/W: 3.64 Avg: 488.6 I/s: 262.4 Sh: 1.17 1.00 93 + 2018-04-28 21:06:57| GPU3 64C Sol/s: 547.5 Sol/W: 2.75 Avg: 536.0 I/s: 286.9 Sh: 1.24 1.00 78 2018-04-28 21:07:00| GPU2 38C Sol/s: 122.8 Sol/W: 2.26 Avg: 174.4 I/s: 64.0 Sh: 0.37 1.00 78 ++ 2018-04-28 21:07:00| GPU1 59C Sol/s: 494.8 Sol/W: 3.32 Avg: 496.8 I/s: 266.2 Sh: 1.24 1.00 85 ++* 2018-04-28 21:07:10| GPU5 50C Sol/s: 211.3 Sol/W: 2.37 Avg: 254.4 I/s: 111.8 Sh: 0.55 1.00 78 + 2018-04-28 21:07:10| ========== Sol/s: 2402.5 Sol/W: 2.84 Avg: 2485.8 I/s: 1278.1 Sh: 5.84 1.00 84 2018-04-28 21:07:16| GPU0 65C Sol/s: 539.9 Sol/W: 2.72 Avg: 535.5 I/s: 285.3 Sh: 1.27 1.00 93 2018-04-28 21:07:16| GPU4 64C Sol/s: 480.4 Sol/W: 3.64 Avg: 488.6 I/s: 261.9 Sh: 1.17 1.00 93 2018-04-28 21:07:17| GPU3 64C Sol/s: 533.1 Sol/W: 2.75 Avg: 536.0 I/s: 285.5 Sh: 1.24 1.00 78 2018-04-28 21:07:20|> GPU2 57C Sol/s: 406.8 Sol/W: 2.26 Avg: 174.8 I/s: 220.4 Sh: 0.37 1.00 78 2018-04-28 21:07:20|> GPU1 59C Sol/s: 499.1 Sol/W: 3.32 Avg: 496.9 I/s: 265.6 Sh: 1.24 1.00 85 2018-04-28 21:07:30|> GPU5 57C Sol/s: 532.7 Sol/W: 2.37 Avg: 255.0 I/s: 288.2 Sh: 0.55 1.00 79 + 2018-04-28 21:07:30| ========== Sol/s: 2992.1 Sol/W: 2.84 Avg: 2486.7 I/s: 1606.9 Sh: 5.83 1.00 84 2018-04-28 21:07:36|> GPU0 64C Sol/s: 524.3 Sol/W: 2.72 Avg: 535.5 I/s: 284.9 Sh: 1.27 1.00 93 2018-04-28 21:07:36|> GPU4 64C Sol/s: 496.0 Sol/W: 3.64 Avg: 488.6 I/s: 261.8 Sh: 1.17 1.00 93 2018-04-28 21:07:38|> GPU3 64C Sol/s: 538.1 Sol/W: 2.75 Avg: 536.0 I/s: 285.6 Sh: 1.23 1.00 78 2018-04-28 21:07:40| GPU2 62C Sol/s: 528.3 Sol/W: 2.27 Avg: 175.5 I/s: 286.4 Sh: 0.38 1.00 80 ++ 2018-04-28 21:07:40| GPU1 59C Sol/s: 488.7 Sol/W: 3.32 Avg: 496.8 I/s: 262.7 Sh: 1.24 1.00 85 2018-04-28 21:07:50| GPU5 60C Sol/s: 533.1 Sol/W: 2.37 Avg: 255.5 I/s: 283.5 Sh: 0.55 1.00 79 2018-04-28 21:07:50| ========== Sol/s: 3108.5 Sol/W: 2.84 Avg: 2487.9 I/s: 1664.9 Sh: 5.83 1.00 84
And here is typical GPU usage and temp graphic: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fpreview.ibb.co%2FiVix1x%2Fscreenshot_22.png&t=665&c=i1ZA3YpkGMn3jQ) One more question, dstm. Could you add temperature limit option for GPU emergency shutdown (like in Claymore)? The reason for having such option is that your temperature controller works best with 100% fan setting, but it destroy fan very quickly. So it's sometimes good to have PID on fan and hard temp° limit to be sure GPU will turn off if exceed the limit. Concerning zm's temperature controller. Fan speed of 100% isn't necessary required, it's more important to have a reasonable constant fan speed - otherwise you'll get two controlling loops - which isn't optimal. I've changed the description of the 'temp-target' option to reflect this in recent zm versions. Emergency shutdown: Yes, I can add something like this. However what exactly should happen after the temp-limit is reached on one of the GPUs? should zm terminate immediately? Also don't forget, a user-space program can't guarantee you to react properly with respect to this (the hardware or the driver can get unresponsive) - however it should work in most cases.
|
|
|
|
dstm (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 02, 2018, 02:13:43 PM |
|
Is there a function in dstm to restart the computer if the mining speed falls under a select value? In claymore you can set up that the miner restarts after 5min if the hash falls below the chosen value.
How can I set up this function in dstm, in the readme file they are no comment about this..
ZM doesn't have something like this. I don't think this is a good idea. You could end up in a reboot loop - this can damage your hardware. I think a better solution is to implement a notification system - e.g. ZM could execute a configurable script when certain conditions arise.
|
|
|
|
dstm (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 02, 2018, 02:14:31 PM |
|
I would like to incorporate your miner into some software, but I really need to know immediately when shares are accepted. Any plans to implement a verbosity or similar?
I can add this if it's important - what's the use case for immediate notification of accepted shares?
|
|
|
|
|