-
Notifications
You must be signed in to change notification settings - Fork 650
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
[Dashboard] Improve ordering by size performance #14647
Comments
UpdateI've made a couple of PoC to check if there is any improvement:
The results is the following: Current performanceImproved performanceAs you can see there is a huge improvement using that new function, a magnitude order with accounts having a great number of tables. What's next?Well, there is a lot to do: Be sure if we want to go on with this improvement because we need to spend more time here and implies multiples parts (@alonsogarciapablo / @javitonino ). If we decide to go on we have to:
|
WOW. That looks like a huge improvement @ethervoid! Does it only help with "ordering by size" or with retrieving maps / datasets in general? |
@alonsogarciapablo this would help in the ordering part for calls to the What do you mean for retrieving maps/datasets? |
I was basically asking if this will only help when ordering by size, or also in other calls to /viz (eg: when loading latests maps and datasets for the home page). |
This will only help for the ordering part |
Hey @ethervoid! How is this going? Are we still working on it? Thank you! 🙇 |
This has been stopped. There were still a lot of work to do and there is no backenders working on the dashboard as of now. |
Closing for now. Let's reopen is this becomes an issue. |
Context
Ordering datasets by size take a huge amount of time to apply
Steps to Reproduce
Current Result
Now it takes, in my test account, either ~47seconds or a timeout error
Expected result
Reduce that amount of time considerably
// @alonsogarciapablo
The text was updated successfully, but these errors were encountered: