This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
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.
Allow configuration of Synapse's cache without using synctl or environment variables #6391
Allow configuration of Synapse's cache without using synctl or environment variables #6391
Changes from 32 commits
99ab65a
d684ec8
135fdaa
f36f3ab
73cfdeb
babf4ea
e55591d
c580eb3
f888515
a14831d
50fcb4a
8439ce5
92d4d13
d70be18
c11c8ad
0e368ee
f7ec526
e174b2d
946650c
9735a08
c76a412
0a02b2a
a21702f
125c5a0
0b069b7
a96b5d9
2f4dbfa
ac020de
18c1dbf
4aeb6fb
5f508e7
2619891
0fc0a7d
965e259
f004cee
546c23e
7117b89
4ed7aa1
be0737a
14fbf27
cc1dd98
de25659
6e979a1
fec13be
905c833
f300c08
28f7f59
5f3eddc
fcc9c3a
5acca12
fdef3ad
ca98241
48709a9
9e3a9ba
fa56e16
83cf583
424215a
c7f3bf6
485f177
fe89050
ae6070b
4448633
f8ed432
c1b339b
06fbfc2
edb04df
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
it was just a handy way of making it scale for larger instances. The logic went that if you're running a larger instance, you'll bump your cache factor, and will probably want a bigger connection pool too. it's a bit of a hack, but otoh I didn't want to have millions of options that you have to tune.
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.
So we're changing this to match the event cache size rather than allowing it to be configured separately? This feels like something that should be considered separately (and we should think how to support things that have already configured these).
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.
in the installs I've seen it, the cache for
get_relations_for_event
and such needs to be closer to the event cache size than zero, since a lot of times in sync or whatever, for each event it will also look for the relations and aggregations for it. It was the major thrashing candidate.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 can believe that, though on matrix.org I've noticed that that's not true on a lot of workers. I'd be tempted to remove it and we can add it back with a way of overriding this behaviour if you set a per cache factor override.