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

[Yarik47]

Great improvement over EWBF of 5% across all my 6 x 1070 however dstm crashes every few moments as the .bat is on loop the miner restarts.

I find it strange why it crashes as with EWBF it is running for well over a month without issues?

This is most likely due to overclocking, you have to readjust it, zm puts a different load on your GPUs.

Ok, I will try to retweak my overclocked settings and try again...

I also very often falls dstm. and very much rejected .. overclock cleaned, does not help ..

[1714039849]

1714039849

[dstm]

I'm having issues launching zm, I already created links to the newer versions of the libraries. On Centos 7.3

ln /usr/lib64/libcrypto.so /usr/lib64/libcrypto.so.1.0.0
ln /usr/lib64/libssl.so /usr/lib64/libssl.so.1.0.0

I still get the error

./zm: /lib64/libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by ./zm)
./zm: /lib64/libssl.so.1.0.0: version `OPENSSL_1.0.0' not found (required by ./zm)

Any help?

dstm, can you compile you miner using the library and not the specific version?

ZM depends on openssl 1.0.x, that's not the newest - the newest is 1.1.. It looks like your /usr/lib64/libssl.so has the wrong version, most likely it's 1.1.0.

Btw. I had to downgrade openssl to 1.0.0 because Ubuntu still uses the old version.

[dstm]

I'm somewhat unhappy with 0.5.3, I've discovered 2 bugs so far. If it's unstable for you use 0.5.2 pls. I'm rechecking it's changes.

Friend, could you check performance on gtx1080 ? It's don't have increased performance to compare EWBF miner.

I have advantage on 1060, 1070, 1080ti around 5%, but 1080 have same score or less than ewbf's miner.

And please add uptime timer in browser telemetry.
Tnx you very much.

P.S. GDDR5X trash? Any chance to get some advantage from this type of memory in your miner?

Uptime was already requested multiple times, I'll add it ofc.

Bandwidth test I've done suggest that GDDR5X based GPUs are capable to reach about 70% of their theoretical bandwidth limit, GDDR5 bases GPUs about 80%.

[dstm]

Great improvement over EWBF of 5% across all my 6 x 1070 however dstm crashes every few moments as the .bat is on loop the miner restarts.

I find it strange why it crashes as with EWBF it is running for well over a month without issues?

This is most likely due to overclocking, you have to readjust it, zm puts a different load on your GPUs.

Ok, I will try to retweak my overclocked settings and try again...

I also very often falls dstm. and very much rejected .. overclock cleaned, does not help ..

I had some reports about crashes after I released the windows version, however it seems that after people have readjusted their overclocking their issues were gone.
I've also no reports about unusual high reject rate.

Could you pls provide more information.
What OS, zm version, pool, how high is the reject rate, how does it crash etc.
Stability is of high priority.

[Andrey09]

https://i.imgur.com/VaDUmwr.jpg

After some times i see what my preformance is significantly reduced. This does not cause any error. It only works at 1% of its capacity.

[Yarik47]

Great improvement over EWBF of 5% across all my 6 x 1070 however dstm crashes every few moments as the .bat is on loop the miner restarts.

I find it strange why it crashes as with EWBF it is running for well over a month without issues?

This is most likely due to overclocking, you have to readjust it, zm puts a different load on your GPUs.

Ok, I will try to retweak my overclocked settings and try again...

I also very often falls dstm. and very much rejected .. overclock cleaned, does not help ..

I had some reports about crashes after I released the windows version, however it seems that after people have readjusted their overclocking their issues were gone.
I've also no reports about unusual high reject rate.

Could you pls provide more information.
What OS, zm version, pool, how high is the reject rate, how does it crash etc.
Stability is of high priority.

OS Windows 10 64bit, zm version 0.5.3, pool nicehash, reject rate 3815/65 accepted/rejected, falls every 3-6 hours, writes overclocking, but overclocking is removed..
still noticed that the current hash is very different from the average!
http://ipic.su/img/img7/fs/1.1509222667.jpg

[dstm]

After some times i see what my preformance is significantly reduced. This does not cause any error. It only works at 1% of its capacity.

Do you use some kind of restart script? After a crash - such that there are still other zm instances running.                  
If you had a crash, e.g. after doing some tests, I recommend to reboot your system, the driver might not work properly after a crash.
                                                                                                                              
GPU4 doesn't report it's pwr consumption properly, does nvidia-smi show proper values? The driver might not work propely.

[dstm]

Great improvement over EWBF of 5% across all my 6 x 1070 however dstm crashes every few moments as the .bat is on loop the miner restarts.

I find it strange why it crashes as with EWBF it is running for well over a month without issues?

This is most likely due to overclocking, you have to readjust it, zm puts a different load on your GPUs.

Ok, I will try to retweak my overclocked settings and try again...

I also very often falls dstm. and very much rejected .. overclock cleaned, does not help ..

I had some reports about crashes after I released the windows version, however it seems that after people have readjusted their overclocking their issues were gone.
I've also no reports about unusual high reject rate.

Could you pls provide more information.
What OS, zm version, pool, how high is the reject rate, how does it crash etc.
Stability is of high priority.

OS Windows 10 64bit, zm version 0.5.3, pool nicehash, reject rate 3815/65 accepted/rejected, falls every 3-6 hours, writes overclocking, but overclocking is removed..
still noticed that the current hash is very different from the average!
http://ipic.su/img/img7/fs/1.1509222667.jpg

You'll get a higher reject rate on nicehash because they are submitting new jobs very often. ZM prepares work for the GPUs in advance, this is for performance reasons, it is especially helpful ins situation where you have cpu spikes caused by other processes. So if you get a new job it might happen that your solve a share for a previous job.
                                                                                                                              
If you look at the average values, you'll see that they are increasing, since your current sol/s value is higher - so your performance was slower previously, maybe because some background process used cpu.

Edit: ZM writes also more details if it fails in this particular case, could you please provide the whole message?

[mirny]

Could you add the option of selecting mining devices?

That option is already implemented, I'm using it like that.
Just read the readme file carefully, it's not that long, you will find it for sure...

[jdubya]

Great work on the miner.

I know CPU usage is an issue...but I'm running the latest version and my CPU usage is around 90% at all times.  Is this still normal?


Also, is there a way to configure the start.bat file so the miner will mine from 2 or more different pools?  Designate some cards to 1 pool and the remainder to another?  Or do you have to open 2 instances of the miner with 2 different start files?  I'm pretty sure my CPU couldn't handle that..LOL

[dstm]

Great work on the miner.

I know CPU usage is an issue...but I'm running the latest version and my CPU usage is around 90% at all times.  Is this still normal?


Also, is there a way to configure the start.bat file so the miner will mine from 2 or more different pools?  Designate some cards to 1 pool and the remainder to another?  Or do you have to open 2 instances of the miner with 2 different start files?  I'm pretty sure my CPU couldn't handle that..LOL

How much of it does zm consume?

Yes, you have to open 2 instances.

[jdubya]

Great work on the miner.

I know CPU usage is an issue...but I'm running the latest version and my CPU usage is around 90% at all times.  Is this still normal?


Also, is there a way to configure the start.bat file so the miner will mine from 2 or more different pools?  Designate some cards to 1 pool and the remainder to another?  Or do you have to open 2 instances of the miner with 2 different start files?  I'm pretty sure my CPU couldn't handle that..LOL

How much of it does zm consume?

Yes, you have to open 2 instances.

With the miner running my CPU usage is 88%.  The main draws are: system=37%  CMD processor 29%  System Interrupts 17%

With the miner off my CPU usage is 6-8%

Using EWBF my system interrupts are around 4% and total CPU usage is around 50%

[grendel25]

Are there any flags/options to adjust intensity?  

I have a computer that is just a little laggy when this runs and I'd like some independent control over how hard it works.  I just have a couple of 750ti cards in that one and it slows down quite a bit.  on this computer I have a couple of 1070 cards and no issues whatsoever.  edit: doesn't seem to be a cpu usage thing... cpu is only like 2-3%.  Just seems like an intensity thing.

[ivakar]

well, I wonder if you can push more sols from 1080ti, this tricky 5X memory fails to have good latency(
but there are rumors that a special miner for 1080ti is exist which pushes 1000-1200 sols! your can produce about 800 sols @ crazy settings, the normal figures like 750-770, almost same as ewbf..
if you can achieve more improvements for 1080ti, I guess it is ok to put more fee for 1080ti owners.. like 5% instead of 2%...

[kuksaab]

I'm not sure I understand it correctly - could you pls explain this a bit more.

I think what he means is that when telemetry fails to start due to whatever reason, miner won't start either. I noticed that as well, for me though it wasn't a problem.

Right, zm exits if it can't bind the telemetry server to a socket. I designed it this way to make sure your telemetry settings are correct before it starts mining.

concerning miner auto-start on (re)boot .....my experience is somewhat different

I am not able to autostart ZM with an entry in Cinnamon's Startup Application because on boot-up I always get 'telemetry binding failed' ,
however contrary to the above posting and your confirmation that ZM was designed to abort in that case - my miner starts up 'in the background' ...and in the end it turns out that the telemetry is also active!
What is disturbing is that after the (apparently misleading) message 'telemetry binding failed' ...the terminal falls back to the shell prompt.....and
no output from the actually running ZM is displayed afterwards.

It is even stranger, that if I run the same autostart entry directly from the Startup Application (my Cinnamon Startup Application has besides Add/Edit/Remove also a 'Run immediately' button perhaps new to Mint 18.2) then  ZM starts succesfully....reports that telemetry is started  and happily floods the terminal with the miner's output afterwards.

The command in Startup Application is:

Code:

gnome-terminal --tab -e "/bin/bash -c '/home/.../dstm/zm_0.5.3/zm --server eu1-zcash.flypool.org --port 3333 --user t1xxxxx.Worker --pass d=32000 --temp-target 70 --telemetry=0.0.0.0:51000; exec /bin/bash -i'"  --working-directory="/home/..../dstm/zm_0.5.3"

I tested autostarting ZM with setting even delays up to 90 sec...to no avail.


kuksaab
---------------------------------
6 x GTX 1070 Rig
Linux Mint 18.2 GNU/Linux 4.10.0-37-generic, Cinnamon
dstm's ZCash Miner v0.5.3

[raven1322]

What proxies do you guys use (if any)? Not really fan of connection per card architecture, forgive me dstm.

That's the purpose of this thread, if there is anything that needs improvement or is more usable for you this is the right place to ask.

I’m not quite familiar with the technicalities of mining algorithms, but what is advantage/disadvantage of connection per card architecture vs otherwise? Could this be the reason for increased cpu usage?

Let me try to educate Say you have 20 rigs with 5 cards each. 100 cards. With ewbf or other miners, it would use 20 connections since there is one per rig. Now, with dstm miner 100 cards = 100 connections. Only 5 times more, right? Now imagine 10 guys with 100 cards = 1000 cards = 1000 connections to pool server. Pool servers could detect this as attack and start dropping or throttling connections... Also, there is only 64k ports and server can take around 60k connections per second (in theory).

Thats why I am not fan of this approach (not meaning to be mean or discourage dstm, again sorry man), because it stresses network more, and pool servers too. That is one of the reason some big miners use proxy, to decrease network infrastructure and pool server load.

Someone correct me if this is BS, but with years in sysadmin and networking, it should be legit

The argument about ports is valid, it might be an issues for people with several 10000GPUs on nat-networks. However I guess they would use a proxy anyway.

It doesn't put more stress on the network, since there is roughly the same amount of data (depending on how the pool adjusts difficulty) going through the network, zm's bandwidth requirements are very low. It also doesn't put more stress on nat-routers, since they have to rewrite the same amount of data.

Pool side: right it puts more stress on pools since they have to manage more clients.

In general, if there are good arguments for an improvement/change, I'll think about them ofc, so this kind of discussions are welcome.

Thank you very much for the knowledge and education. I’m not really one of those hundred or thousand card guys though, that’d be too much. But this informion is helpful in general to the whole mining community.

[UrsaUrsa]

@dstm: pool closes connection (pool sexy), zm tries to reconnect, connects but freezes and errors out when setting difficulty. Any ideas?

[Supercoiner111]

@dstm: pool closes connection (pool sexy), zm tries to reconnect, connects but freezes and errors out when setting difficulty. Any ideas?

me too I am getting the same issue with pool.sexy, any help would be appreciated...

[UrsaUrsa]

@dstm: pool closes connection (pool sexy), zm tries to reconnect, connects but freezes and errors out when setting difficulty. Any ideas?

me too I am getting the same issue, any help would be appreciated...

My solution is leaving pool sexy. What's the point of the low fee if you are having to restart your miner every 3 hours.im just gonna wait for my next payout.
@dstm, if you could look into this anyhow that would be brilliant.

[pttinh]

Could you add the option of selecting mining devices?

That option is already implemented, I'm using it like that.
Just read the readme file carefully, it's not that long, you will find it for sure...

Ahh, got it. Thanks.
At the first time, I think --dev is an option for development.