It's the error message like it was returned by the server.

The accepted share ratio and the Avg. Sol/s change - especially if something goes wrong.


I'm not sure what you mean by 'spin up'. ZM uses all available GPU 'power' right from the start.

I've tried to explain the disadvantages it has in my previous post. They are especially visible in your scrolling example.
https://bt.irlbtc.com/view/2021765.msg25716313#msg25716313


This might happen if something consumes GPU-time when you start the miner, e.g. if it's also used to render the screen.       
This is how an average value works mathematically, it doesn't detect something there is also no way to speed up it, since it wouldn't be an average anymore.

Same here, a little annoying to have multiple workers on NH stats page but not a deal breaker, it still has better performance than NH Excavator and EWBF. When i start the miner i get a lot of "Share above target" but after a few minutes it works like a charm.

Just upgraded to 0.5.6 a few minutes ago, will report back later.

That's why i stated above "like on the web interface", i was speaking about how the console actually look. I obviously use the telemetry already, but just if we want a "cleaner" console.

Really want to hear what dstm think about this. Maybe the best suggestion so far.

Sorry, I didn't see your reply. I was focused on second post.
On the one hand you've right to see it in a compact form, hovewer on the other hand it doesn't look clearly becuse there are too much "compressed" informations. Like --time parameter, maybe could you think about disabling few of printfs such as iterations and shares?

Later I will think on other proposal how to get it look more clearly if u don't mind.

It is logical, hovewer I'm connected to iGPU (integrated graphics). So it is strange because no one program - except miner - interfere with graphics card.

I know, but as I've shown on my gif the average looks a bit strange in my case because it's increasing and increasing for many hours until it will achieve it's operating point. In my opinion taking into consideration latest 100-200 records (circular buffer) should be fine.


---------------------------------------------
edit:
This is what I said before: I had been disconnected from suprnova pool and few minutes after reconnect my hashrate started from ~530:
https://i.imgur.com/egeP7La.png

Thx for the suggestion. I don't want to depend on javascript unless it provides something very useful. The webui works currently pretty well even on terminal based browsers which don't support javascript.
There are not that many lines you have to check also you have usually to check each GPU as a whole separately - so I don't think this provides real benefits.

Anyone got frequently hashrate drop problem recently (Drop to 0 in about 20 mins, but when I checked miner, it still hashing as normal)? Look like after few days, it happen again to all of my miners. I mined in flypool, asia1 server, port 3333.

anyone having issues with 12 cards running in DSTM on linux? works fine with ewbf/ anything I need to add or change?

edit had to reboot and just seems slow to load the cards, but its running now hope its stable pickedup ~200 hashes over ewbf ~8070-8270

Matches with the binary.