Author

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

full member
Activity: 350
Merit: 126
Plate with inscription about error is bad idea. Need write error to log file end close program. In my *.bat file next command is reboot, and if program close after error, rig is not stop, but will reboot and continue work.

I'll add logfile support.                                                                                                     
Rebooting on error is bad idea you might end up in a reboot loop which can damage your hardware.
full member
Activity: 350
Merit: 126
OK, I have tested it myself as well, I got some imporvent for my two 1070 - instead of showing 470 sol/s they are now showing 500!!
goood!!  but on my other farm with 1080ti the performance degraded,  from 750 sol/s tom 732 sol/s  -- baad((

I wonder could be the reason CPU? for 1070 rigs there is i7@3700, while for TI rig it is pentium @2500?
I have to make more testing I guess!

anyway, thanx for miner!  Roll Eyes

Yes this is most likely because of the slower CPU.
full member
Activity: 350
Merit: 126
Is there a way to exit immediately if connection to the pool is lost?

Currently not, I'll add an option to disable reconnection.
member
Activity: 74
Merit: 20
ZM.EXE has stopped working. Please fix this, I get this problem once a day and miner can't reset itself. I need to click "OK" on this error and only then it starts again. Can you update it, so even when there is this error it can start again
full member
Activity: 196
Merit: 100
Plate with inscription about error is bad idea. Need write error to log file end close program. In my *.bat file next command is reboot, and if program close after error, rig is not stop, but will reboot and continue work.
full member
Activity: 168
Merit: 100
OK, I have tested it myself as well, I got some imporvent for my two 1070 - instead of showing 470 sol/s they are now showing 500!!
goood!!  but on my other farm with 1080ti the performance degraded,  from 750 sol/s tom 732 sol/s  -- baad((

I wonder could be the reason CPU? for 1070 rigs there is i7@3700, while for TI rig it is pentium @2500?
I have to make more testing I guess!

anyway, thanx for miner!  Roll Eyes

What model of 1070 do you have? And what are your overclock settings?
full member
Activity: 266
Merit: 111
OK, I have tested it myself as well, I got some imporvent for my two 1070 - instead of showing 470 sol/s they are now showing 500!!
goood!!  but on my other farm with 1080ti the performance degraded,  from 750 sol/s tom 732 sol/s  -- baad((

I wonder could be the reason CPU? for 1070 rigs there is i7@3700, while for TI rig it is pentium @2500?
I have to make more testing I guess!

anyway, thanx for miner!  Roll Eyes
newbie
Activity: 14
Merit: 0
Great miner thanks. Also testing on 2 rigs and so far about 5% increase can’t wait to see what more you can do to push some more sols out of it
full member
Activity: 336
Merit: 100
8 hours - no crash, brilliant. about 6% faster than EWBF's , but i run only on very low overclocks and 65% TDP to maximize hs/w ratio. Guess the difference is bigger if you OC more.

I applaud you, sir. I get 19kH/s++ on my farm instead of 17.8kH/s with EWBF miner
newbie
Activity: 4
Merit: 0
I'm also having problems with invalid shares...
newbie
Activity: 45
Merit: 0
Is there a way to exit immediately if connection to the pool is lost?
full member
Activity: 171
Merit: 105
It is a very CPU-heavy miner, but I am not sure what effect it has on sols.

Hadn't noticed this until it was pointed out. Will this perhaps be optimized in a future release? I'm currently using the GPU rigs' CPUs to mine some other coin..
full member
Activity: 336
Merit: 100
Definitely will give this one a try later today. +8% would be awesome! will report back after testing.
full member
Activity: 168
Merit: 100
It is a very CPU-heavy miner, but I am not sure what effect it has on sols.
sr. member
Activity: 476
Merit: 278
Does this miner gives 5-10% lower sols if rig have a shity cpu on it like it was on ewbf miner?
full member
Activity: 168
Merit: 100
ZOTAC 1070 8gb Mini 5-card Rig:
Power: 64%
Core Clock: +225
Memory Clock: -220
55% Fans
= Average 2065 sols @ 568w at the wall

Happy to have ditched EWBF for a faster miner with an active developer  Wink


Interesting that you are turning DOWN your memory clock. I see better results when I increase it it.

So you're getting around 413Sol per card at about 3.64Sol/W? Pretty sure you could improve that, but I don't know your electricity costs.

Here's my 7 card Asus DUAL OC GTX 1070 rig with
power at 90%,
voltage at +30,
core clock +96 and
memory +480:



I think that primary graphics card is getting a little unstable with overclocking the core. My other cards on that rig seem fine overclocked to +120.


My 6x Gigabyte Windforce GTX 1070s allow even greater overclocking but I still need to find a better Sol/W point.
They have:
power at 88%
voltage at +35%
Core clock at +144
Memory at +610

For some reason the telemetry won't load in the browser right now, but watching it on the screen I am at 2964Sol/sec with 3.14Sol/sec, averaging 494Sol/sec per card.

newbie
Activity: 17
Merit: 0

I have a "load-problem" under ubuntu 14.04 with 4 Nvidia Cards on CUDA9:
(used latest 0.52 Version)

2121 root      20   0 51,978g 396036 351052 S 23,4  9,8   0:56.68 ./zm --server .....

compared with the older ewbf-miner 23,4% nearly continous load on a quad-cpu is huge.
I costs nearly 8 Watts extra energy. Can you please check, why the cpu-usage is so high ?

my used commandline:

./zm --server luckpool.org --port 3057 --user xxx.yyy --pass x --time

Tested with --api and without --time i have the same results with the cpu-load
full member
Activity: 168
Merit: 100
How does it crash? Does the system freeze?                                                                                     
Is anybody else having stability issues?

Sometimes the system just instantly shuts down, no warning or error/BSOD.
Other times it seems the primary graphics card fails - nothing comes out of display and I need to press the power button/alt-f4 as windows is still running, then only when the Windows 10 shutting down screen comes on do I actually see anything appearing on the screen. This is the most common thing.


However, I turned the overclock settings even further down and I think I have found a stable point. I think there may be one graphics card in the rig which is a little less stable than the rest, as my 6x Gigabyte Windforce 1070s are running very smooth at 2938Sol/sec (around 490Sol/sec per card) while the 7x ASUS Dual OC 1070s are running at 3224Sol/sec (around 460Sol/sec per card) at about 3.41W/Sol.


The MSI Duke in my desktop delivers a very consistent 500Sol/sec, so between my 14 cards I am at 6662Sol/sec averaging just over 475Sol/sec per card.


All in all, very happy with how the miner is working. Even though the ASUS cards are not getting quite the same results, they're still performing better than they did with ewbf and at considerably lower W/Sol.
newbie
Activity: 60
Merit: 0
on the windows version, do you create a config file for pool information or?

***  figured it out ***

 bat file
newbie
Activity: 41
Merit: 0
+ Does the temp controller overtake AB fan control, as I understand when OP says "It is recommended to set your fan speed to 100% when using this setting.", or am I totally wrong ? So far, it does not, and fans just run at max speed. I definitely don't want to use 100% fans, they usually run at 45% max, and I'm pretty fine with that.

No it doesn't. ZM's temperature controller is a proper PID-controller - it measures the temperature and adjust the performance continuously. Fans on the GPU use also some kind of controller. So you'll get 2 controlling loops with feedback. So what might happen is: zm lowers the performance -> fan gets slower -> temp rises again -> zm lowers the performance even more -> fan gets slower again .... and so on - something like this or something in between might happen. You don't have to set the fan speed to 100% however it should be set to something constant to avoid 2 controlling loops.

Yep, cool, I'll give it a try.

+ Is there a way to use different colors to separate displayed information ?

Currently not. What information is hard to read currently / should be highlighted?

Maybe 1 colour for the ============ line could be easier to read.

+ Maybe worth implementing an auto-restart function, as during a 1h network maintenance, I found my rigs had exited the program. Short connection shortage restart as soon as it re-connects, but longer ones seem to just exit.

Currently zm retries for about 10min and gives up. This is hardcoded. It exits after 10min such that you'll get notified if you're using notifications on process exit.

I personally don't use it, maybe an opportunity to be a bit less of a lazy fuck, and get things sorted. But I admit that knowing EWBF's reconnecting no matter what makes me a bit more relax. Don't sweat it, we'll manage. You obviously have enough bread on your plate, at the moment...

HUGE thanks to you, for your work, your fast and systematic answers, good support is always much appreciated. More than happy to share my 2%. Hope it makes your work worth it.
Jump to: