bench(event cache): add a benchmark for measuring how long it takes to handle a sync update #5435
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.
Each sync update contains N rooms (for N in 1, 10, 100), each gets 1000 new room message (text) events. We might want to do something more representative, as we've done in other benchmarks (throw a few aggregated events in the mix), but for now that'll be sufficient, and it's already teaching us things, notably that the supposed performance improvement in #5426 isn't the obvious improvement I thought it would be. More investigation is needed there, so in the meantime I'll just add a comment that it's not as good as it was supposed to be.