Skip to content
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

perf: Optimize initializing chart from cube #1697

Closed
wants to merge 1 commit into from

Conversation

bprusinowski
Copy link
Collaborator

Potentially closes #1658

This PR removes fetching of all dimensions with values in favor of re-using a cube preview query when initializing a chart from cube. I am not 100% convinced it improves the performance in a visible way, but at least we removed a potentially expensive query in favor of the preview one, that only fetches one dimension value for every dimension.

Copy link

vercel bot commented Aug 29, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
visualization-tool ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 29, 2024 10:17am

Copy link
Contributor

@noahonyejese noahonyejese left a comment

Choose a reason for hiding this comment

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

LGTM ✔️, Even if it doesn't perform much better visually, the query was pretty expensive..., however CI is failing several checks.

@bprusinowski
Copy link
Collaborator Author

Ah, good catch @noahonyejese :) I forgot to mock the response for DataCubePreview query in tests, so some of them fail 🤦‍♂️ I will fix them, however no code was modified in DataCubeObservations query, I assume this check failed due to LINDAS being unstable, which happens quite frequently 😅

@noahonyejese
Copy link
Contributor

Ah, good catch @noahonyejese :) I forgot to mock the response for DataCubePreview query in tests, so some of them fail 🤦‍♂️ I will fix them, however no code was modified in DataCubeObservations query, I assume this check failed due to LINDAS being unstable, which happens quite frequently 😅

Yeah I've noticed that LINDAS is quite unstable sometimes....

@bprusinowski
Copy link
Collaborator Author

Closing in favor of #1890

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

possible filter and components query needlessly fires twice - and takes a very long time
2 participants