[ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows)

[dstm]

can anyone help me with this?

dstm exited, waiting to cooldown a bit

on linux

'waiting to cool down' is not a message produced by zm, are you using some kind of monitoring process?

[1713946923]

1713946923

[1713946923]

1713946923

[1713946923]

1713946923

[dstm]

Is it normal for hash rate to drop by half on DSTM miner console, NOT on pool hash rate. I am mining equihash on nicehash or miningpoolhub.

I cant understand why it does this. The gpus are not overheating or crashing. It is just a massive reduction in hash rate that's fixed by reboot of console.

It changes the difficulty rate and then drops.

I'm having the same issue trying v0.5.6 and v0.5.7.  It starts out around 4,600 Sol/s and it slowly drops to around 2,000 Sol/s over the course of a couple of hours.  Running SMOS and have tried mining several equihash coins at a couple of different pools with the same results.  Rebooting makes it go back up to 4,600 Sol/s it then it slowly drops down again.  Temperatures are all <55C with a target of 75C.  Servers seem to be changing GPU difficulties often.  Overclocks set to 0 while I try to figure this out.

Same issue here, playing card roulette right now. It seems to only happen when one of my cards is in, what I have done so far:
1. Removed all overclocks
2. Watt use is at 110 for 1070ti's, 120 for 1070, and 200 for 1080ti's (note: all hash rates drop, the 1080ti's in particular hit the 500's)
3. Swapped entire riser on suspect gpu
4. Swapped pci ports, tested pci port with alternative gpu
5. Looked at wattage use of cards when they drop, cards all drop power down well below my set wattage. So the power drop I think is the cause of  less hash, what's causing the power drop I am unsure of.

Smos
dtsm 0.5.6 (trying 5.7 now)
10 cards currently (have had various amounts between 9-13)
h110 pro btc

EDIT: So far so good on new version, but judging by change log this is just luck right now.

I have the same issue.

Hashrate decreases after running a time (few hours).

Tested on SMOS dstm-v0.5.8 (0.5.7, 0.5.6 is same)
5 Rig P106-100 x12 (on main H110 Pro BTC)

When the hashrate dropped, the screen appeared a lot of duplicated share message, at the same time cpu usage is very high.

However, sometimes I can run nearly a day that hashrate not decrease.

Judging by the reports this seems to affect SMOS users only.
How do you monitor the solution rate on SMOS, does it provide a custom interface?
Could you also pls provide the output of the 'top' command sorted by cpu usage and the output of nvidia-smi, before and after the solution rate drop?

OK. I can moniter SMOS via ssh client (putty)

Test on SMOS (P106-100 x12) Non OC Power Limit: 80W
dstm-v0.5.8

Best regards.

Thx, for providing this data.                                                                                                  
You have a lot 'nvidia-settings' processes running in your 'After top' output. This could be the reason for the performance drop.

[dstm]

dstm Any chance we can get a simple function where you can load the options from a file? Say --config or -c option pointing to a file? Will be huge help. It's probably a 10-15 minute job tops (Though haven't seen your specific code).

I'm using another miner which allows that, but gives me only slightly lower profit. It's the only thing stopping me from changing my ~6100 H/s rigs to use your miner. (I really can't do without this option).

Configuration file is something I can add ofc. However how is a configuration file different from using shell scripts to configure the parameters?

[dstm]

SUGGESTION

After several reconnections the api crashes and don't work anymore. Can you add a trigger like a key stroke to reload the api server?

Could you pls describe this in more detail? How do you access the telemetry data? What is actually not working. If there is a bug the proper way is to fix it, not providing a restart key.

I run zm on Windows 10 1709 (great work by the way) with telemtry on port 2709 and i constantly monitor it via web browser (i also made a little C# app to query over json-rpc).

Currently i have issues with my broadband connection dropping several times a day and my ISP have me scheduled for a visit after several support calls. That being said, zm works fine, up time reaches over days but conn time resets every time my modem restarts the connection with my ISP, still telemetry works fine when connection is restored, but after about 2 days of this dropped connections the telemtry just stops working via web browser or my c# app. I ran this tests on the rig itself, even telnet cant open a connection. I "know" i has to be the connection issue but when the telemtry dies i have to log in to the rig and restart zm. Definitely not a deal breaker but maybe i just have to live with it while my ISP fix my line.

Thx for the description, I'll try to reproduce this, it sounds like a bug in zm.

[dstm]

Is there a way to show watts pulled from each card in the log file?

The logfile doesn't contain this information. You can access the average and current power consumption of each GPU via json-rpc - also the web-ui reports average power consumption for each GPU.

[dstm]

Tried the miner.
When running it had faster hash rates than EWBF but on 2 different rigs (win10) miner crashed / exited without any warning.

Seems to be reporting faster numbers than EWBF but this version is not stable enough for me.
I'll maybe try later after some time and versions.

This is most likely due to overclocking - you have to readjust it.

[marco.ruiz]

can anyone help me with this?

dstm exited, waiting to cooldown a bit

on linux

'waiting to cool down' is not a message produced by zm, are you using some kind of monitoring process?

I beleive that is a HiveOS whatchdog message. Maybe your OC settings are quite high, try lowering a bit, remember every miner needs a little bit of tuning. If it stills crashes you can ask for support on its thread.

[blackjec]

Linux x64:
sha1 827b137e061fe1da8f8fbcea12cec22449d3ae13
https://drive.google.com/file/d/19fSFYqoeOhOkxQqKnGpNI3n-7TIppHnq
https://mega.nz/#!vx0QgQ7K!dG2hbzh1KINYsqL9v75YlxpKwq0U7KaualMN6uFW2JY

but both file has 42f586f88866fa6d41e3e1cb91614c6e638b0905 sha1 checksum

[marco.ruiz]

Linux x64:
sha1 827b137e061fe1da8f8fbcea12cec22449d3ae13
https://drive.google.com/file/d/19fSFYqoeOhOkxQqKnGpNI3n-7TIppHnq
https://mega.nz/#!vx0QgQ7K!dG2hbzh1KINYsqL9v75YlxpKwq0U7KaualMN6uFW2JY

but both file has 42f586f88866fa6d41e3e1cb91614c6e638b0905 sha1 checksum

You need to compare agaist zm sha1 hash, not the zip file.

[dyils]

dstm Any chance we can get a simple function where you can load the options from a file? Say --config or -c option pointing to a file? Will be huge help. It's probably a 10-15 minute job tops (Though haven't seen your specific code).

I'm using another miner which allows that, but gives me only slightly lower profit. It's the only thing stopping me from changing my ~6100 H/s rigs to use your miner. (I really can't do without this option).

Configuration file is something I can add ofc. However how is a configuration file different from using shell scripts to configure the parameters?

Alternatively, automatically loading a config from a file named a certain way would also be useful. It's more convenient for me as I have multiple rigs, with some shared storage (NFS) where I usually put configuration files of different miners. Allows me to have one file and edit one file, which will apply the changes to all miners. Unfortunately, my rigs weren't originally used or created for mining, but I struck a really nice deal, so I actually have a pretty high number of machines with a low number of GPUs per machine, which makes management a bit of a pain.

I am also giving access to one of the machines to some friends in alternate accounts for non-compute intensive things. One of them, for example, is hosting a teamspeak server. The rigs are kind of, multi-use, I guess. Passing a file helps not only with convenience but also with privacy. I don't want them to be seing what I'm doing as I'm making a decent amount of money out of this. Compared to my country's very low wages, this is an enourmous profit in addition to my regular salary, which I'd rather people who know me didn't know about.

Don't know if that makes sense to you. It's convenience + privacy and I'm not willing to give those up for the extra $5-6 per month I'll be making with your miner. Though as I said, wages are low and if you did add that one thing, I'd be more than happy to switch.

Thanks

[marco.ruiz]

dstm Any chance we can get a simple function where you can load the options from a file? Say --config or -c option pointing to a file? Will be huge help. It's probably a 10-15 minute job tops (Though haven't seen your specific code).

I'm using another miner which allows that, but gives me only slightly lower profit. It's the only thing stopping me from changing my ~6100 H/s rigs to use your miner. (I really can't do without this option).

Configuration file is something I can add ofc. However how is a configuration file different from using shell scripts to configure the parameters?

Alternatively, automatically loading a config from a file named a certain way would also be useful. It's more convenient for me as I have multiple rigs, with some shared storage (NFS) where I usually put configuration files of different miners. Allows me to have one file and edit one file, which will apply the changes to all miners. Unfortunately, my rigs weren't originally used or created for mining, but I struck a really nice deal, so I actually have a pretty high number of machines with a low number of GPUs per machine, which makes management a bit of a pain.

I am also giving access to one of the machines to some friends in alternate accounts for non-compute intensive things. One of them, for example, is hosting a teamspeak server. The rigs are kind of, multi-use, I guess. Passing a file helps not only with convenience but also with privacy. I don't want them to be seing what I'm doing as I'm making a decent amount of money out of this. Compared to my country's very low wages, this is an enourmous profit in addition to my regular salary, which I'd rather people who know me didn't know about.

Don't know if that makes sense to you. It's convenience + privacy and I'm not willing to give those up for the extra $5-6 per month I'll be making with your miner. Though as I said, wages are low and if you did add that one thing, I'd be more than happy to switch.

Thanks

You can create a "bootstrap" file wich downloads a hosted bat file or copy from a shared folder a remote bat file then execute it.

[donpablo]

You could easily include any config file in a shell script and call zm with the parms you like...

Just switched to 0.5.8, its running very well :-)
Thanks for the great job !!

This is from a Gigabyte Gaming 1070Ti:

>  GPU0  59C  Sol/s: 501.7  Sol/W: 4.10  Avg: 490.7  I/s: 262.1  Sh: 3.63   1.00 47  ++
   GPU0  58C  Sol/s: 490.5  Sol/W: 4.10  Avg: 490.7  I/s: 262.1  Sh: 3.44   1.00 47 
>  GPU0  59C  Sol/s: 491.6  Sol/W: 4.10  Avg: 490.7  I/s: 262.1  Sh: 3.28   1.00 47 
   GPU0  59C  Sol/s: 482.7  Sol/W: 4.09  Avg: 490.4  I/s: 262.1  Sh: 3.27   1.00 42  +

[AzzAz]

You could easily include any config file in a shell script and call zm with the parms you like...

Just switched to 0.5.8, its running very well :-)
Thanks for the great job !!

This is from a Gigabyte Gaming 1070Ti:

>  GPU0  59C  Sol/s: 501.7  Sol/W: 4.10  Avg: 490.7  I/s: 262.1  Sh: 3.63   1.00 47  ++
   GPU0  58C  Sol/s: 490.5  Sol/W: 4.10  Avg: 490.7  I/s: 262.1  Sh: 3.44   1.00 47 
>  GPU0  59C  Sol/s: 491.6  Sol/W: 4.10  Avg: 490.7  I/s: 262.1  Sh: 3.28   1.00 47 
   GPU0  59C  Sol/s: 482.7  Sol/W: 4.09  Avg: 490.4  I/s: 262.1  Sh: 3.27   1.00 42  +

Cool for gigas. Please settings?

[jpl]

Interesting,.. mine looks like this now.  4 Asus and 2 EVGA 1070's....(Win10 64 bit)  .. not sure if it's decent or not yet.  Stable at a bit lower settings.

   GPU2  73C  Sol/s: 444.4  Sol/W: 3.98  Avg: 443.2  I/s: 238.9  Sh: 1.51   1.00 172
   GPU3  73C  Sol/s: 481.2  Sol/W: 3.64  Avg: 473.8  I/s: 250.4  Sh: 1.37   0.97 188
   GPU4  73C  Sol/s: 476.3  Sol/W: 3.92  Avg: 471.0  I/s: 251.6  Sh: 1.55   1.00 172 +
   GPU5  64C  Sol/s: 478.5  Sol/W: 3.33  Avg: 479.1  I/s: 257.4  Sh: 2.11   0.98 167 +++
   ========== Sol/s: 2840.6 Sol/W: 3.64  Avg: 2820.8 I/s: 1509.7 Sh: 9.79   0.99 172
   GPU0  71C  Sol/s: 491.6  Sol/W: 3.38  Avg: 488.4  I/s: 262.2  Sh: 1.74   1.00 195 ++
   GPU1  73C  Sol/s: 463.4  Sol/W: 3.57  Avg: 465.3  I/s: 249.5  Sh: 1.57   1.00 1047 +
   GPU2  73C  Sol/s: 438.2  Sol/W: 3.98  Avg: 443.1  I/s: 234.3  Sh: 1.53   1.00 265 +
   GPU3  73C  Sol/s: 481.4  Sol/W: 3.64  Avg: 473.9  I/s: 254.0  Sh: 1.39   0.97 172 +
   GPU4  73C  Sol/s: 468.9  Sol/W: 3.92  Avg: 471.0  I/s: 251.9  Sh: 1.53   1.00 172
   GPU5  64C  Sol/s: 490.1  Sol/W: 3.33  Avg: 479.2  I/s: 257.2  Sh: 2.19   0.98 208 +++
   ========== Sol/s: 2833.5 Sol/W: 3.64  Avg: 2821.0 I/s: 1509.0 Sh: 9.95   0.99 343
   GPU0  71C  Sol/s: 495.9  Sol/W: 3.39  Avg: 488.4  I/s: 262.0  Sh: 1.72   1.00 195
   GPU1  73C  Sol/s: 462.3  Sol/W: 3.57  Avg: 465.3  I/s: 249.4  Sh: 1.55   1.00 1047
>  GPU2  73C  Sol/s: 437.7  Sol/W: 3.98  Avg: 443.1  I/s: 236.8  Sh: 1.51   1.00 265
>  GPU3  73C  Sol/s: 475.5  Sol/W: 3.64  Avg: 473.9  I/s: 254.9  Sh: 1.38   0.97 172
>  GPU4  73C  Sol/s: 474.3  Sol/W: 3.92  Avg: 471.1  I/s: 251.7  Sh: 1.55   1.00 172 +
>  GPU5  64C  Sol/s: 486.7  Sol/W: 3.33  Avg: 479.3  I/s: 257.3  Sh: 2.17   0.98 208
   ========== Sol/s: 2832.5 Sol/W: 3.64  Avg: 2821.1 I/s: 1512.2 Sh: 9.87   0.99 343
>  GPU0  71C  Sol/s: 490.0  Sol/W: 3.39  Avg: 488.5  I/s: 262.3  Sh: 1.77   1.00 203 ++
>  GPU1  73C  Sol/s: 460.7  Sol/W: 3.57  Avg: 465.2  I/s: 249.4  Sh: 1.53   1.00 1047
   GPU2  73C  Sol/s: 441.9  Sol/W: 3.98  Avg: 443.0  I/s: 237.6  Sh: 1.49   1.00 265
   GPU3  73C  Sol/s: 469.7  Sol/W: 3.64  Avg: 473.9  I/s: 251.3  Sh: 1.39   0.98 251 +
   GPU4  73C  Sol/s: 483.5  Sol/W: 3.92  Avg: 471.2  I/s: 251.7  Sh: 1.53   1.00 172
   GPU5  64C  Sol/s: 475.1  Sol/W: 3.33  Avg: 479.3  I/s: 257.4  Sh: 2.14   0.98 208
   ========== Sol/s: 2820.8 Sol/W: 3.64  Avg: 2821.1 I/s: 1509.7 Sh: 9.86   0.99 357

[kps9727]

Is it normal for hash rate to drop by half on DSTM miner console, NOT on pool hash rate. I am mining equihash on nicehash or miningpoolhub.

I cant understand why it does this. The gpus are not overheating or crashing. It is just a massive reduction in hash rate that's fixed by reboot of console.

It changes the difficulty rate and then drops.

I'm having the same issue trying v0.5.6 and v0.5.7.  It starts out around 4,600 Sol/s and it slowly drops to around 2,000 Sol/s over the course of a couple of hours.  Running SMOS and have tried mining several equihash coins at a couple of different pools with the same results.  Rebooting makes it go back up to 4,600 Sol/s it then it slowly drops down again.  Temperatures are all <55C with a target of 75C.  Servers seem to be changing GPU difficulties often.  Overclocks set to 0 while I try to figure this out.

Same issue here, playing card roulette right now. It seems to only happen when one of my cards is in, what I have done so far:
1. Removed all overclocks
2. Watt use is at 110 for 1070ti's, 120 for 1070, and 200 for 1080ti's (note: all hash rates drop, the 1080ti's in particular hit the 500's)
3. Swapped entire riser on suspect gpu
4. Swapped pci ports, tested pci port with alternative gpu
5. Looked at wattage use of cards when they drop, cards all drop power down well below my set wattage. So the power drop I think is the cause of  less hash, what's causing the power drop I am unsure of.

Smos
dtsm 0.5.6 (trying 5.7 now)
10 cards currently (have had various amounts between 9-13)
h110 pro btc

EDIT: So far so good on new version, but judging by change log this is just luck right now.

I have the same issue.

Hashrate decreases after running a time (few hours).

Tested on SMOS dstm-v0.5.8 (0.5.7, 0.5.6 is same)
5 Rig P106-100 x12 (on main H110 Pro BTC)

When the hashrate dropped, the screen appeared a lot of duplicated share message, at the same time cpu usage is very high.

However, sometimes I can run nearly a day that hashrate not decrease.

Judging by the reports this seems to affect SMOS users only.
How do you monitor the solution rate on SMOS, does it provide a custom interface?
Could you also pls provide the output of the 'top' command sorted by cpu usage and the output of nvidia-smi, before and after the solution rate drop?

OK. I can moniter SMOS via ssh client (putty)

Test on SMOS (P106-100 x12) Non OC Power Limit: 80W
dstm-v0.5.8

Best regards.

Thx, for providing this data.                                                                                                  
You have a lot 'nvidia-settings' processes running in your 'After top' output. This could be the reason for the performance drop.

Just to add my voice to this list, I'm also an SMOS user experiencing the same issue.  HOWEVER, it's only on my 13 card 1070 rigs (H110).  I have a 6 card 1060 rig (Z270-A) that has been running for days with no drop in performance, also on SMOS.

Thanks for being responsive!

[Protofabtt]

Awesome work! Loving 0.5.8 it fixed a protocol error our miners on our pool were receiving when mining ZCL. Greatly appreciate the hard work put into making this miner - https://minez.zone

Any advice on which pol to mine ZCL and which exchange is good for it?
thx

[wetblanket]

Any advice on which pol to mine ZCL and which exchange is good for it?
thx

Random answer for you: suprnova.cc and zclmine.pro both have ZCL pools.  Bittrex has ZCL wallets.

But really, you can find this stuff yourself!

[Protofabtt]

Any advice on which pol to mine ZCL and which exchange is good for it?
thx

Random answer for you: suprnova.cc and zclmine.pro both have ZCL pools.  Bittrex has ZCL wallets.

But really, you can find this stuff yourself!

I asked as I am seeking advice that's better than 'go find out for yourself'.

I didn't join the forum to be offered 'random' answers.

[TONY_GUN]

SUGGESTION

After several reconnections the api crashes and don't work anymore. Can you add a trigger like a key stroke to reload the api server?

Could you pls describe this in more detail? How do you access the telemetry data? What is actually not working. If there is a bug the proper way is to fix it, not providing a restart key.

I run zm on Windows 10 1709 (great work by the way) with telemtry on port 2709 and i constantly monitor it via web browser (i also made a little C# app to query over json-rpc).

Currently i have issues with my broadband connection dropping several times a day and my ISP have me scheduled for a visit after several support calls. That being said, zm works fine, up time reaches over days but conn time resets every time my modem restarts the connection with my ISP, still telemetry works fine when connection is restored, but after about 2 days of this dropped connections the telemtry just stops working via web browser or my c# app. I ran this tests on the rig itself, even telnet cant open a connection. I "know" i has to be the connection issue but when the telemtry dies i have to log in to the rig and restart zm. Definitely not a deal breaker but maybe i just have to live with it while my ISP fix my line.

Thx for the description, I'll try to reproduce this, it sounds like a bug in zm.

I already wrote in this topic about the problem. So can confirm it. I have 2 rigs. Both of them has the problem with the telemetry server (dstm v0.5.6 and v.0.5.7 tested). It becomes unavailable after 5-10 successful connections. If I start miner and do not try to connect to the server even couple days, and after that I do 5-10 successful connections, it becomes unavailable. If I try to connect (5-10 times) just after 5 minutes after the miner started, it becomes unavailable too until I'll restart it. I hope you'll understand what I mean, despite my bad eng.

[donpablo]

You could easily include any config file in a shell script and call zm with the parms you like...

Just switched to 0.5.8, its running very well :-)
Thanks for the great job !!

This is from a Gigabyte Gaming 1070Ti:

>  GPU0  59C  Sol/s: 501.7  Sol/W: 4.10  Avg: 490.7  I/s: 262.1  Sh: 3.63   1.00 47  ++
   GPU0  58C  Sol/s: 490.5  Sol/W: 4.10  Avg: 490.7  I/s: 262.1  Sh: 3.44   1.00 47 
>  GPU0  59C  Sol/s: 491.6  Sol/W: 4.10  Avg: 490.7  I/s: 262.1  Sh: 3.28   1.00 47 
   GPU0  59C  Sol/s: 482.7  Sol/W: 4.09  Avg: 490.4  I/s: 262.1  Sh: 3.27   1.00 42  +

Cool for gigas. Please settings?

200C/700M/120W

Are there any better ?