Skip to content

Conversation

@KitsuneRal
Copy link
Member

It's used to find events and resolving duplicates - pretty performance- sensitive therefore. Caching it can save up to 10% on larger chunks of event processing. The trade-off is that the footprint of each room event is now 56 bytes instead of 32 but JSON for each event is much larger than that (usually hundreds of bytes) so I think that's reasonable.

It's used to find events and resolving duplicates - pretty performance-
sensitive therefore. Caching it can save up to 10% on larger chunks of
event processing.
@KitsuneRal KitsuneRal added the performance Things taking too long to get done label Sep 30, 2025
@sonarqubecloud
Copy link

Copy link
Member

@TobiasFella TobiasFella left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, the trade-off sounds fair.

@KitsuneRal KitsuneRal merged commit d211eb4 into dev Oct 8, 2025
11 checks passed
@github-project-automation github-project-automation bot moved this from In work to 0.10 - Done in libQuotient 1 Oct 8, 2025
@KitsuneRal KitsuneRal deleted the kitsune/cache-event-id branch October 8, 2025 11:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

performance Things taking too long to get done

Projects

Status: 0.10 - Done

Development

Successfully merging this pull request may close these issues.

3 participants