ok, some quick observations after running for about 8 hours or so.
Short version - miner reports great hashrate, better then any other i tried so far. However, the pool likes to jack up the worker diff way too high, choking out smaller rigs.
Long version:
Trying on a total of 10x1070's spread across one main rig, and some random boxes.
box 1 - win 7, single gpu. (worker 1)
box 2 - win 10, single gpu. (worker 4)
box 3 - win 7 2xgpu (worker 2)
box 4 - win 10 6xgpu. (worker 3)
All gpu's are tuned with exactly the same settings - +125 core, +500 mem, 60%tdp (110w) in afterburner. These were my go to settings for zcash and lbry, so i left them alone for now All get just over 29mh on skunk, according to the miner.
However, and this is especially true for the single and 2x gpu machines, the pool difficulty ends up being too high. The single gpu's started out at pool diff of 64 (worker at 0.25), which from my previous experimenting is the sweet spot for a single 1070 gpu, and then eventually ended up at diff of 256 (worker at 1). At 256 the card chokes. When the nethash is nice and steady, the card is still able to submit work ever 2-3 sometimes 4 blocks. When whatever is hitting this coin hits it hard (when you see the nethash double in like 5 minutes) the card can't keep up with fast moving blocks at all. There was a time when i caught a glimpse at the miner and saw at least a good dozen blocks go by before the card was able to submit any work. There were instance that the card was so chocked, the pool would show that a worker dropped out, meaning that the card submitted no shares in whatever time interval the pool uses to calculate hash. In fact, as i'm typing this i can see the miner window on my single gpu boxes, and one of them just had about 10 blocks go by without any work submitted (diff 256 pool, 1 at worker).
It's a similar story for the 2xgpu box. The diff started off at 128, which again i think is a sweetspot for this setup, but then climbed to 512. At that diff, just like the single gpu setup, too many blocks go by before a share is submitted and the cards choke.
6xgpu rig seems to be not as affected by this. It started off at 256, then eventually climbed to 640. It too misses out on blocks, and hashrate reported at the pool jumps around wildly, but at least it's able to get some shares in every other block or so.
Overall, i am very happy with the miner. The pool is finding blocks at a good clip, and with good efficiency, so maybe this approach of jacking up the worker diff works. But it feels wrong to see this many bunches of blocks go by without a share submitted. To me it means that my gpu's are not even competing to find a solution to a whole lot of blocks. You can't solve a block if you don't at least compete to solve it.
As i was finishing typing this, another 6 blocks went by before my single gpu rig submitted a share. That means that this particular gpu didn't even compete for 6/7th of the opportunities to find a block.
this is great ...
positive results and criticism ...
the results seem to be quite good - especially stability ...
the aggression the pool stratum has - we are tuning it to the algo ... this is why at times you will see the miner stop for a few seconds - while adjustments are being made ...
we are working diligently to resolve all any issues - as well as work towards a better system with both miner and pool ...
much appreciated ...
#crysx