-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add feature to stagger sector prove commit submission #10543
Conversation
storage/pipeline/commit_batch.go
Outdated
time.Sleep(builtin.EpochDurationSeconds * time.Second) | ||
sectorsProcessed = 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd try to avoid the sleep in any way possible.
Polling api.ChainHead every 2-3s, and looking for height change is probably good enough
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Out of curiosity, why should we try to avoid sleep? And what would be the difference between the 2 approaches? Seems like they'd have the same end result of waiting for around an epoch
Co-authored-by: Łukasz Magiera <magik6k@users.noreply.github.com>
…n-project/lotus into sbansal/max-prove-commits-submit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, would be great to test on a real setup
Related Issues
#7002
Proposed Changes
Add a config to allow SPs to stagger sector prove commit submissions
This is done because gas estimates for ProveCommits are non deterministic and increasing as a large number of sectors get committed within the same epoch resulting in occasionally failed msgs. Submitting a smaller number of prove commits per epoch would reduce the possibility of failed msgs
Additional Info
Checklist
Before you mark the PR ready for review, please make sure that:
<PR type>: <area>: <change being made>
fix: mempool: Introduce a cache for valid signatures
PR type
: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, testarea
, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps