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

See? I'm glad you finally found out yourself 

In the new version 0.6.0, do not expect an increase in performance?

0.6 has it. It's priority based, zm switches to the pool with the highest priority after it gets reachable again.

I suggest you to ask this on the SMOS forum.


This is not an error. It's there to make debugging easier in case something goes wrong with ssl connections.



What version are you on? Previous zm versions had a reconnect timeout - current version doesn't.

This might be the effect of CPU frequency scaling - especially since rigs 6/7/8/9 have same hardware. It's optimal (optimal with respect to power cosumption) for the cpu to reduce it's clocks as much as possible. You'll see a higher cpu utilization ofc if the cpu is running on low clocks. Try to disable CPU frequency scaling / set it to performance mode to get reliable data.

You are talking of the new 0.6 DSTM version since a lot of time.
You told that 0.5.8 version to be a temporary version.
When do you think releasing 0.6 version and what will be new with it ?
Thank you.

Thanks for the points - suggestions are welcome ofc.


do you mean difficulty should be mapped to a smaller range such that it's easier to read? Float is a datatype representing real numbers it's not related to the radix/base that's used for representation.


I'm not sure why you have them impression it's 'just a status message' - it's actually much simpler to print events on a separate line - simply at the time they happen. Currently zm collects all the performance data and events for each GPU separately during a period of time. It calculates averages etc. and presents it in a compact structured way - otherwise you'll end up with a lot of unstructured spam on your ui.


What details are you missing? And how is it related to tools you would not need otherwise?

It does.


What per share details are useful and what's the use case for it? This would require to print each share on a separate line. If it's useful - I'll restructure the logfile format ofc.


It's in the logs such that you're able to check if something was affecting the performance on your rig in the past which helps debugging performance issues.


Now that's is a very useful information. If there are any regressions between the versions - pls report them - I can't fix them otherwise and they might appear in later versions too. How much did the cpu load increase for you?

Any chance to add pool failover support @dstm?. With EWFB I can setup several pools in case one of the fails

I won't increase it.

ZM needs some additional work I was previously not focusing on - this delays the release of 0.6 unfortunately.

Thank you tytanick.

Yes, that's the result of unstable hardware.
I'll improve the error message in this particular case such that zm reports the affected GPU.

https://bitcointalksearch.org/topic/m.29004024

Hi

Does the --target-temp feature work in simplemining?
It seems smos is overriding that miner option.

 I receive 'ssl want write' error when using an ssl connection. It happens on two separate pools. It happens intermittently.

How can I set miner to reload when internet connection fails? sometimes if internet connectivity is unstable then the miner does not recover and begin working properly again. It kind of times out.
 
Please advise.

lol u cant use pools numbers to compare. once ur up and once down.

Hashrate reported by the pool is calculated with the shares you send -> not precise.
Hashrate reported by the miner -> real hashrate (if you trust the dev)

There... less smart words. Do you understand?

Better run your own tests... Lots of smart words put in one sentence but have no meaning all together.

You cannot compare hashrate reported by the pool so precisely.
It is calculated with the actual shares that you send.

Therefore, it vary depending on the day you mine, the difficulty, the number of miners, the pool hashrate,  network congestion, the latency, luck factor, and so on...
Too many parameters for a 50sols difference over 3000sols.

Just rerun your tests and you'll see that you wont get the exact same numbers.

Lul, guys here were right you are pretty stupid. Not stupid but actually dumb 3099 is actual numbers from pool. But of course brain dead people does not read or actually try something, they just whine all around

Congrats @dstm
You are about to be included in NiceHash Miner thats 100K + users.
https://github.com/nicehash/NiceHashMinerLegacy/commits/master

Keep up the good work!