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.
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
Filter added to Admin-API GET /rooms #17276
Filter added to Admin-API GET /rooms #17276
Changes from all commits
34454ad
712e3d1
f09d000
c55b638
b886ca4
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.
Is it possible to estimate whether two more joins will have a significant impact on performance?
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.
We can
EXPLAIN ANALYZE
the query on a sizeable Matrix deployment, such as matrix.org.Running the following query:
which gives us:
(Note that I only analyzed after ensuring that a bare
EXPLAIN
would not be too costly.)This is indeed fairly slow, and takes up a connection for nearly a whole second. As these filters are only using data from
room_stats_state_current
, do we really need the secondINNER JOIN rooms USING (room_id)
?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 based the implementation on existing code (e.g. get_users_paginate_txn) The second join is used to determine the number of public or non-public rooms in the case of filtering. Perhaps it is also possible to determine the state of the flag via the events, but I would assume that this is not faster.
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 see. In that case
rooms
is required. I've created a separate issue to track the slow performance of these queries: #17330Otherwise this codepath is only hit for the
/rooms
admin API. Thus I think we can live with a slower, but more useful query.