-
Notifications
You must be signed in to change notification settings - Fork 490
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
Optimize Dataverse page, to issue fewer queries and load faster. #2777
Comments
I can see 2 areas of QA process for this issue:
for best results the same db should be used. |
(a new build is needed; i've already made a commit today) |
OK, there are following known limitations/things that may be messed up:
But it is fast!! lol I have solutions for these things; will wire them on Friday. Really had to leave today. |
Missing from the harvest card is the harvested icon on the dataset card but the linked icon instead and a note at the bottom that reads: |
For tabular data, for comparison on what is missing, for the same file: production: 4.2.2: |
I am going to take the list of to-do items from both Leonid's comment and Kevin's comment, and combined them here. Please add additional items here, for one easy to read checklist, rather than a running dialog of new comments.
|
Benchmark summary: |
|
😵 |
Tabular data files: cards should now have proper display of UNF, var counts, etc. |
Cards for harvested dataverses and datasets should be properly formatted now. |
Cards for harvested files should also be properly formatted now. |
Linked objects - should now be displayed properly. |
File categories - should now be displayed in the file card. |
Per @mheppler 's list of TODO items: To the best of my knowledge, all the issue have been resolved. |
A few things.
Here's how the current "File Tag" facet ("categories" in the code looks in production as of v. 4.2.1): Here's how you can edit "File Tags" vs "Tabular File Tags": Here's the DataTags homepage/branding: I don't have any objection to indexing Tabular Data Tags in principle but I want us to think about the use of the word "tags". It feels overloaded to me already, and we haven't integrated DataTags yet (#871). /cc @mcrosas @eaquigley |
Found some issues:
All that's left for this ticket is tabular data tags, opened as a separate ticket. Closing this ticket. |
Just an info update: So yeah, 10:1 reduction or better, in query numbers... |
That issue is #2802 |
Dataverse page still issues 1,200+ queries to load the default home page in production.
Custom/native queries can be used to speed things up. (Raman already worked out some solutions for the mydata page).
Also, an important subtask of this is #2776 - optimizing handling of thumbnails. This alone generates a surprising number of database requests; hence it has a dedicated ticket of its own.
fyi: Card attribute list can be found under "Next Steps": #2474
The text was updated successfully, but these errors were encountered: