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.

Sign up for GitHub

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

Jump to bottom

Two example queries that require a lot of RAM (one uses wdt:P31/wdt:P279*) #730

Closed
WolfgangFahl opened this issue Aug 9, 2022 · 2 comments
Closed

Two example queries that require a lot of RAM (one uses wdt:P31/wdt:P279*) #730

WolfgangFahl opened this issue Aug 9, 2022 · 2 comments

Comments

@WolfgangFahl
Copy link

WolfgangFahl commented Aug 9, 2022 •
edited
Loading

Examples for out of memory conditions:

grafik
@hannahbast
Copy link
Member

The problem with these queries is that the result without the GROUP BY is huge. For example, for the second query, it's over a billion triples. It's aggravated by the fact that the implementation for the predicate path is not very space-efficient.

I wonder if these queries work for any of the other engines around.

@hannahbast hannahbast changed the title Out of memory on the qlever public endpoint Two example queries that require a lot of RAM (one uses wdt:P31/wdt:P279*) Aug 27, 2022
@hannahbast
Copy link
Member

This was more an observation. Yes, some queries are very expensive, and QLever imposes a memory limit and there will be an error message when that limit is exceeded by a query.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@WolfgangFahl @hannahbast