Speed up concise_* tables calculation#13331
Open
gregorbg wants to merge 20 commits intothewca:mainfrom
Open
Conversation
Member
|
This has nothing to do with the Ranks Single or Ranks Average table right? |
Member
Author
|
Right. You're probably talking about #13293, which is an entirely separate PR |
2 similar comments
Member
Author
|
Right. You're probably talking about #13293, which is an entirely separate PR |
Member
Author
|
Right. You're probably talking about #13293, which is an entirely separate PR |
This was referenced Feb 16, 2026
gregorbg
force-pushed
the
feature/speedup-concise-calculation
branch
from
0a25a62 to
cf3a13b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This basically does what the title says. The query itself is not being changed, except for the fact that I've moved the nested query into a "proper" CTE.
The idea is that instead of joining everything for the
GROUP BYon-the-fly, we already have all the data in the records lookup table. This enables indexes which can speed up the grouping significantly.The price that we need to pay is storage space, though.