Add automatic benchmark of storage for full proofs during farming #5064
marcoabreu
started this conversation in
Ideas
Replies: 2 comments
-
Implemented in #5170 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Realistically, if a lookup goes beyond 30s all components should give up and return immediately with an ERROR condition trickled up the stack since even the most optimal proof of space would not be candidate since the SP will have expired. Yet, I see responses in the logs of times double and even triple of that (when there are underlying data access issues). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Right now, we are only notifying the user when the qualities lookup is too slow. In the rare case they are actually having a full proof though, they might run into the issue that their storage is not capable of handling the load and thus they might lose the reward.
Hence, my proposal would be run period automatic benchmarks of a random farmed plot which measures the duration of full proof and lets the user know if their storage is too slow. Thus, we could avoid the frustrating situation that a user has a bunch of plots but never actually receives the rewards, but they could never figure out why.
This pays into #3188
Beta Was this translation helpful? Give feedback.
All reactions