Accepted hashrate

[slawek]

Hello, unfortunately, please help please

What to do with this
Accepted hashrate: 5.97M

Rejected hashrate: 0

Efficiency: 100.00%
  


IN THIS same time with me
   | 11.18 / 16.01 / 15.91Mh / s |

Regards Slawek.

but that it is also fairly often
   | 16.69 / 16.13 / 16.42Mh me



the pool
Accepted hashrate: 13.12M

Rejected hashrate: 0

Efficiency: 100.00% but he is a big difference
am i wrong ???

Hot greetings from Polish

[kires]

I'm seeing the same thing as our friend Slawek here... I think.

Since last evening at about 6 PM EST, both my rejected percentage and total hash rate dropped markedly as reported server-side. It looks like the server just stopped reporting/displaying the vast majority of rejected shares. My reported reject rate is now around 1%, which would be great except my total hash rate is fluctuating wildly, but seems to be averaging about 20-25% below what I see mining straight LTC. Before this last big release, I would have chalked it up to the idle restart issue... but that ought not to be an issue any more. I'm curious as to whether the efficiency drop I'm seeing is the result of an issue that can be resolved, or if it's just to be expected mining with a multipool as opposed to straight LTC.

[Chris Sokolowski]

I believe that this is caused by a bug that Steve corrected last night and just needs to release today. I will point him to this post so that he can provide more insight.

[kires]

Excellent and Than-q!

[Steve Sokolowski]

I'm seeing the same thing as our friend Slawek here... I think.

Since last evening at about 6 PM EST, both my rejected percentage and total hash rate dropped markedly as reported server-side. It looks like the server just stopped reporting/displaying the vast majority of rejected shares. My reported reject rate is now around 1%, which would be great except my total hash rate is fluctuating wildly, but seems to be averaging about 20-25% below what I see mining straight LTC. Before this last big release, I would have chalked it up to the idle restart issue... but that ought not to be an issue any more. I'm curious as to whether the efficiency drop I'm seeing is the result of an issue that can be resolved, or if it's just to be expected mining with a multipool as opposed to straight LTC.

I looked into this issue this morning.

The rejected hashrate drop is correct. Previously, there were shares being rejected incorrectly because the server was comparing them to the wrong difficulty. 1% seems to be about average.

On the other hand, the total hashrate should not have dropped. I'll investigate that and see what I can find. The work restart time for your miners is only 1s, so it may be that the cause of the problem is not related to work restarts at all. Would it be correct to say that the total hashrate is simply the same 20-25% lower as it was before this update, which would indicate that the issue with your miners was never resolved?

[kires]

Would it be correct to say that the total hashrate is simply the same 20-25% lower as it was before this update, which would indicate that the issue with your miners was never resolved?

Yes, that's what it looks like to me.

[Steve Sokolowski]

We released a new version just a few minutes ago, and we fixed many issues. We're unsure whether your problem is resolved or not.

How are things working now?

[kires]

It took it's time getting up to speed, but it seems more stable now than before. I'll know better after a few hours, of course, but it looks pretty good at the moment

[kires]

Nope. Whatever the issue is, it's still in place.

[kires]

Also, maybe a silly question, but I should set "no-submit-stale": false, right?