-
Notifications
You must be signed in to change notification settings - Fork 299
Small perf improvement to limited incremental sync #17149
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
base: develop
Are you sure you want to change the base?
Conversation
59b8435
to
72e73cb
Compare
72e73cb
to
0c4580d
Compare
cc @richvdh, as this is adding another optimisation on top of the sync state delta work you/we did |
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.
A few questions, but on the whole looks sound.
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.
LGTM. Thanks!
Thinking about it, I'm slightly worried that we don't have tests for this case. I'll need to have a think about how we go about doing that 🤔 |
The idea here is that we often end up fetching enough events from the DB to fill the gap, but we still end up with a gap due to the timeline limit. However, we can still apply the same optimisation as before to the list of fetched events, rather than just the truncated list we return.