-
Notifications
You must be signed in to change notification settings - Fork 3
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
heavy performance regression in preview #1298
Comments
FTR: fixed by |
FTR: same story again on TEST v9.2.1 now with a new dataset.
|
Hi @Rdataflow, I just opened two links you shared (Visualize TEST and LINDAS TEST) and observed the following loading times:
It looks like the performance is the same for both sources. Can you confirm this is also a case on your side? |
we need to reopen - issue revives with new cube
|
Thanks for clarifying @Rdataflow. It looks like the reason for #1285 was to fix some broken cube previews. When checking the broken cube preview from #1285, it's still the case that we have a cartesian product generated when having Technically I could just hard-code to always take the first ten observations, even though the SPARQL query should already return only that. Is there no hope for a proper fix on the database level to avoid workarounds on our side (by fixing the performance we introduce another bug that's not really on our side)? |
@bprusinowski can you share some example queries where you get more results than expected? |
Sure, this is a query that made us introduce #1285 in the first place: https://s.zazuko.com/6AcHrD I am only aware of this one example at the moment, but can't guarantee there aren't more cases like this 👀 |
I asked VSHN to clarify how to fix the observed 1000 results... |
Great, thank you! 💯 |
|
Closing as we have rewritten the preview query completely. |
Describe the bug
following the merge of #1285 there are some heavy performance regressions observed
comparing the response time for this cube, there is a serious regression
To Reproduce
Steps to reproduce the behavior:
Expected behavior
equally fast preview like on INT, i.e. near ~1s
Environment (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: