-
Notifications
You must be signed in to change notification settings - Fork 77
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
analytics/datasets: make query more efficient #1387
Conversation
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.
This looks great, Alex! Easier to read it, and easier for those databases to compute.
There are more changes that might be made, e.g.
However, compared to the other changes here, these feel like micro-optimisations! Current query plan:
|
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.
🚀
Closes #1388
What has been done to verify that this works as intended?
Existing tests/CI.
Why is this the best possible solution? Were any other approaches considered?
This PR improves performance significantly, but also introduces a number of style & formatting changes.
An alternative approach would be to minimise changes in this PR to be 100% performance focussed, and introduce more general changes in other PRs.
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
Should not affect users.
Does this change require updates to the API documentation? If so, please update docs/api.yaml as part of this PR.
No
Before submitting this PR, please make sure you have:
make test
and confirmed all checks still pass OR confirm CircleCI build passes