You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed an issue with the Read (Avg) calculation in the Local mining stats for coordinated mining. The Read (Avg) values seem to be incorrectly calculated across all metrics, while the Hash (Avg) appears to be correct (proportional Data Size).
Here are the stats from three nodes in our coordinated mining setup:
As you can see, the Read (Avg) values don't match the expected values, while the Hash (Avg) seems to be correct. This discrepancy is consistent across all nodes in our setup.
Steps to reproduce:
Set up a coordinated mining environment with multiple nodes
Run the mining process for a sufficient period to gather stable metrics
Compare the reported Read (Avg) values with the expected values based on the node's specifications
Expected behavior:
The Read (Avg) values should closely match the expected values for each node, similar to how the Hash (Avg) values appear to be correct.
Actual behavior:
The Read (Avg) values are significantly different from the expected values, while Hash (Avg) values seem to be correct.
Yeah. I believe we're incorrectly reporting cached reads as reads. Peers batch H1 jobs and sometimes the same recall range will be represented in multiple batches. In those cases we cache the read to avoid going to disk repeatedly. The cached reads probably should not be shown in the report.
I've noticed an issue with the Read (Avg) calculation in the Local mining stats for coordinated mining. The Read (Avg) values seem to be incorrectly calculated across all metrics, while the Hash (Avg) appears to be correct (proportional Data Size).
Here are the stats from three nodes in our coordinated mining setup:
Node1 (exit_node):
Node2:
Node3:
As you can see, the Read (Avg) values don't match the expected values, while the Hash (Avg) seems to be correct. This discrepancy is consistent across all nodes in our setup.
Steps to reproduce:
Expected behavior:
The Read (Avg) values should closely match the expected values for each node, similar to how the Hash (Avg) values appear to be correct.
Actual behavior:
The Read (Avg) values are significantly different from the expected values, while Hash (Avg) values seem to be correct.
Additional information:
The text was updated successfully, but these errors were encountered: