perf: Optimize termsets fetching #1633
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
…into feat/new-termset-triples
…into feat/new-termset-triples
|
the new triples will land on PROD once https://gitlab.ldbar.ch/pipelines/lindas-metadata/-/merge_requests/147 lands in master ... |
...it looks like using VALUES is making the query much slower. As here we always only use one cube iri, we can specify it directly and speed up things significantly.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #1606
This PR optimizes fetching of termsets in every query, in some cases using the new triples (see https://gitlab.ldbar.ch/bafu/visualize/-/issues/684 and https://s.zazuko.com/h7ZwER). Significant performance benefits should be visible on the search page and when looking for mergable cubes.