Author

Topic: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows) - page 120. (Read 224961 times)

newbie
Activity: 3
Merit: 0
Hello!
After update the pool statistc at flypool does not show a name of rig! Could you fix it

Sorry! Was my mistake. All working good Smiley
member
Activity: 336
Merit: 15
Hello anyone tested the new 1070ti on this miner? It should get very decent results. My preorder is delayed unfortunatelly Sad But I expect it should hit over 570 sols.

Please report someone thanks! .)

Why should the new dstm release change anything about the hash rate? Here are my results with v.0.5.2 GPU0 = GTX 1070 Ti the rest GTX 1070


+35 GPU, +500 Memory, 70% PL for the TI, 68% PL for the regular 1070.

That is awfully low I am getting 485 sols @ 135W with normal 1070 cards. You should play with your settings. Also Power Limit is not unified and is totally different for each card so it does not really say anything. The same applies for increases since each card has different stock clocks.

EDIT: I see in the miner your cards are running around 115W thats why the low hashrate.

Right now these are the optimal efficiency settings for me. Next month electricity costs will be lower and I might change my settings.
The 5 GTX 1070 are identical (at least on paper) and the GPU frequency varies only slightly. But at these settings the 1070 Ti GPU is clocked 100 Mhz lower than the regular version.
sr. member
Activity: 463
Merit: 250
Here's mine for what it's worth. Efficiency isn't quite as good, but it's stable enough for a little web browsing on the side. Using the Voltage/Frequency curve seems to be a little more stable for me. 1070 Gaming X



Could you post a screenshot of your curve ? I have never overclocked like that. Could you give please more tips. I have Asus Strix 1070 8g
This is good I would be very interested in 1070ti results at such settings.
sr. member
Activity: 463
Merit: 250
Hello anyone tested the new 1070ti on this miner? It should get very decent results. My preorder is delayed unfortunatelly Sad But I expect it should hit over 570 sols.

Please report someone thanks! .)

Why should the new dstm release change anything about the hash rate? Here are my results with v.0.5.2 GPU0 = GTX 1070 Ti the rest GTX 1070


+35 GPU, +500 Memory, 70% PL for the TI, 68% PL for the regular 1070.

That is awfully low I am getting 485 sols @ 135W with normal 1070 cards. You should play with your settings. Also Power Limit is not unified and is totally different for each card so it does not really say anything. The same applies for increases since each card has different stock clocks.

EDIT: I see in the miner your cards are running around 115W thats why the low hashrate.
member
Activity: 74
Merit: 20
Here's mine for what it's worth. Efficiency isn't quite as good, but it's stable enough for a little web browsing on the side. Using the Voltage/Frequency curve seems to be a little more stable for me. 1070 Gaming X



Could you post a screenshot of your curve ? I have never overclocked like that. Could you give please more tips. I have Asus Strix 1070 8g
full member
Activity: 196
Merit: 100
New Version 0.5.4

fix: device selection
fix: latency reporting
add logfile support
add option to disable auto reconnect
handle disconnect periods in web/json stats
add basic GPU responsiveness infrastructure
ui: change timestamps to ISO 8601 format
webui: report: uptime contime server user port
json: report: uptime contime server user port version


I've restructured some internal parts of zm in this release so pls report if anything doesn't work as expected. Terminal ui has some minor changes most notable the timestamp format - I've changed it to ISO 8601 since it's easier to parse. Logfiles are always appended such that you never lose your previous logs - if you don't want this just delete the previous logfile before starting zm in your scripts.
In this version can miner write only error information? Or write full info from monitor?

in this version is the speed of the miner increased?
newbie
Activity: 8
Merit: 0
Here's mine for what it's worth. Efficiency isn't quite as good, but it's stable enough for a little web browsing on the side. Using the Voltage/Frequency curve seems to be a little more stable for me. 1070 Gaming X

https://imgur.com/8EmeqnT
member
Activity: 336
Merit: 15
Hello anyone tested the new 1070ti on this miner? It should get very decent results. My preorder is delayed unfortunatelly Sad But I expect it should hit over 570 sols.

Please report someone thanks! .)

Why should the new dstm release change anything about the hash rate? Here are my results with v.0.5.2 GPU0 = GTX 1070 Ti the rest GTX 1070


+35 GPU, +500 Memory, 70% PL for the TI, 68% PL for the regular 1070.
sr. member
Activity: 463
Merit: 250
Hello anyone tested the new 1070ti on this miner? It should get very decent results. My preorder is delayed unfortunatelly Sad But I expect it should hit over 570 sols.

Please report someone thanks! .)
newbie
Activity: 6
Merit: 0
Speed is nice but i have problem it still reconnecting +- 3 min over and over.... anyone now how to fix it?

2017-11-05 13:31:03|#  connection closed by server r:0
2017-11-05 13:31:03|#  reconnecting
2017-11-05 13:31:13|#  GPU0  connected to: zen.suprnova.cc:3618
2017-11-05 13:31:15|#  GPU1  connected to: zen.suprnova.cc:3618
2017-11-05 13:31:17|#  GPU2  connected to: zen.suprnova.cc:3618
2017-11-05 13:31:18|#  GPU3  connected to: zen.suprnova.cc:3618
2017-11-05 13:31:20|#  GPU4  connected to: zen.suprnova.cc:3618
2017-11-05 13:31:21|#  GPU5  connected to: zen.suprnova.cc:3618
2017-11-05 13:31:24|#  GPU6  connected to: zen.suprnova.cc:3618
member
Activity: 74
Merit: 20
member
Activity: 154
Merit: 10
What's the dev fee of this miner?
sr. member
Activity: 810
Merit: 444
New Version 0.5.4

fix: device selection
fix: latency reporting
add logfile support
add option to disable auto reconnect
handle disconnect periods in web/json stats
add basic GPU responsiveness infrastructure
ui: change timestamps to ISO 8601 format
webui: report: uptime contime server user port
json: report: uptime contime server user port version


I've restructured some internal parts of zm in this release so pls report if anything doesn't work as expected. Terminal ui has some minor changes most notable the timestamp format - I've changed it to ISO 8601 since it's easier to parse. Logfiles are always appended such that you never lose your previous logs - if you don't want this just delete the previous logfile before starting zm in your scripts.
Ok, thank you.
But no upgrade about the hashrate we are allway at the 0.5.2 version level ?
Improving the hashrate is still the most important.
newbie
Activity: 3
Merit: 0
Hello!
After update the pool statistc at flypool does not show a name of rig! Could you fix it
full member
Activity: 210
Merit: 100
Very nice addition to the telemetry stats... Thanks
newbie
Activity: 55
Merit: 0
dstm, what about problem with incorrect API info (in case of disconnect and crashing of GPU) - have you fixed it in the recent version?
member
Activity: 74
Merit: 20
Already using it. Works so far Cheesy
Now, just work on future versions to try and squeeze more sols from these cards !!! So far, you're great
sr. member
Activity: 392
Merit: 266
EthMonitoring.com
New Version 0.5.4

fix: device selection
fix: latency reporting
add logfile support
add option to disable auto reconnect
handle disconnect periods in web/json stats
add basic GPU responsiveness infrastructure
ui: change timestamps to ISO 8601 format
webui: report: uptime contime server user port
json: report: uptime contime server user port version


I've restructured some internal parts of zm in this release so pls report if anything doesn't work as expected. Terminal ui has some minor changes most notable the timestamp format - I've changed it to ISO 8601 since it's easier to parse. Logfiles are always appended such that you never lose your previous logs - if you don't want this just delete the previous logfile before starting zm in your scripts.

Great, updated EthMonitoring.com also to support latest version.
full member
Activity: 350
Merit: 126
New Version 0.5.4

fix: device selection
fix: latency reporting
add logfile support
add option to disable auto reconnect
handle disconnect periods in web/json stats
add basic GPU responsiveness infrastructure
ui: change timestamps to ISO 8601 format
webui: report: uptime contime server user port
json: report: uptime contime server user port version


I've restructured some internal parts of zm in this release so pls report if anything doesn't work as expected. Terminal ui has some minor changes most notable the timestamp format - I've changed it to ISO 8601 since it's easier to parse. Logfiles are always appended such that you never lose your previous logs - if you don't want this just delete the previous logfile before starting zm in your scripts.
newbie
Activity: 55
Merit: 0
Still no new version with fixed API? Sad(((
Jump to: