Add delays when reading past payment events for stats#3288
Merged
Conversation
When we restart, we load past payments events into the peer stats tracker to inform our scoring algorithm. We read them in chunks, but it can be quite expensive in terms of bandwidth. Since this is low priority and there are a lot of DB reads already happening when starting up, we add a large initial delay and a small-ish chunk delay. With the default values, all past events should be loaded ~20 minutes after starting up, and the first run of the scoring algorithm happens 1 hour after starting up, so this should work well.
pm47
reviewed
Apr 15, 2026
pm47
approved these changes
Apr 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When we restart, we load past payments events into the peer stats tracker to inform our scoring algorithm. We read them in chunks, but it can be quite expensive in terms of bandwidth. Since this is low priority and there are a lot of DB reads already happening when starting up, we add a large initial delay and a small-ish chunk delay.
With the default values, all past events should be loaded ~20 minutes after starting up, and the first run of the scoring algorithm happens 1 hour after starting up, so this should work well.