Rejected Share Reasons

[excelerator]

This is a useful piece of reporting but unfortunately for those with multiple rigs we don't which machine is throwing the errors. Can we get the worker name integrated so we investigate the offending device?

[Steve Sokolowski]

Great suggestion. I can't promise that we can implement this soon, however, because it would increase CPU usage on the mining server to record which worker submitted a share. CPU usage is the limiting factor for the server.

But as soon as we can figure out ways to parallelize the mining server more effectively, we definitely think this is a good idea. Thanks for the suggestion!

[excelerator]

Appreciate putting this on the list! Can you include the timestamp of the event without increasing CPU usage?

[Steve Sokolowski]

The timestamp of the rejected shares?

Timestamp is available and wouldn't increase CPU usage, but it wouldn't make sense in this context. The rejected shares list is a count, and the shares occur at various times, so there isn't any single time to list.

Or, perhaps I'm misunderstanding what you're looking for?

[excelerator]

You're missing nothing - my lack of understanding how it works. Back to school for me.....

I'm just trying to figure out ways to improve machine performance, identify config problems and grow the pool.

You guys are great!

[Chris Sokolowski]

Steve,

I think excelerator wants a list of each individual rejected share with timestamp, which was not part of your original plan but would be useful.