Quote from: andi_21 on September 29, 2017, 05:05:15 PM

Quote from: dstm on September 29, 2017, 12:40:26 PM

I've done a 10h test on flypool: local 79.7 - pool 78.1 79.7/78.1=1.0204. I'll do some more test on different pools with a 10GPU system this week.

Edit:
1-(78.1/79.7) = 0.020075

6x1070 System - local 2632 Sols
flypool: 2540 (24 hours average)
(1-(2540/2632) = 0.03495

Previously i had ~5% difference before flypool changed default diffictulty. Not sure what could be the reason of the remaining 1.495% difference ( 3,495%-2%) but for me low enough to "accept" it without further investigation.

- Is the miner already fully optimized or do you think there is even chance for further optimizations and few more sols/s ?
- miner is stable for me except that outage yesterday as flypool changed default difficulty. (manual restart of miner was necessary)
- could you also put timestamp for each line to console output? i created script to parse output and import data into grafana and timestamp would be usefull. as soon as API is available i wouldnt need it anymore ;-)
- thx for good work and enjoy your dev fee. i plan to use your miner on my 2nd rig as well as soon API is available.

Quote

Previously i had ~5% difference before flypool changed default diffictulty. Not sure what could be the reason of the remaining 1.495% difference ( 3,495%-2%) but for me low enough to "accept" it without further investigation.

Some pool servers are having performance difficulties currently due to the massive increase of solution rate in Zcasch's network - so if you had some disconnects during the 24h period you've lost some shares.
Also I'm using asynchronous queues and prepare some work for GPUs in advance, this is very helpful in situations where your cpu has load spikes, the miner doesn't drop it's solution rate even if you fully load your cpu with other tasks. However the consequence is that if you receive a new job you have some outdated work already in the driver queue which lowers the solution rate as seen by the pool. I've done some more statistics now - the queue sizes are rebalanced now.

Quote

Is the miner already fully optimized or do you think there is even chance for further optimizations and few more sols/s ?

It's pretty well optimized, however I've some more Ideas I wanna try out, they require some more restructuring on the GPU-side however I wanna finish some important stability/feature work first.

Quote

could you also put timestamp for each line to console output? i created script to parse output and import data into grafana and timestamp would be usefull. as soon as API is available i wouldnt need it anymore ;-)

I don't want to put more numbers on the ui, there are already lots of them now ;-). I'm planning to implement logfile support,logfile output will contain timestamps. The dev branch contains already API-support, it will be available in the next release.