-
Hello, Is there documentation to make it production ready which containes (among other things):
Also is there a description of the API ? Finally, what would be the kind of deployment to make it multi-tenant ? Thanks :) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Have a look at the pages linked in the README and the wiki—most pointers come from there.
Check out the performance evaluations for DBLP here and PubChem here. In general, QLever runs well on modern but affordable raw hardware. Every layer of virtualization costs performance. Don’t overthink it—start with what you have and see how it performs. What dataset size are you working with?
Start with the defaults and adjust as needed. If you run out of memory for queries, it likely means QLever isn't optimizing that query type efficiently. The team is interested in such cases to improve performance.
Write support isn’t persistent yet, so the best approach is to keep your original data elsewhere and rebuild the index if needed. This will change within the next six months, but for now, that’s the way to go.
Not much available yet. We're considering adding tracing and heartbeat monitoring in the future.
The API is SPARQL, so it depends on what exactly you’re looking for.
Each dataset needs its own instance. |
Beta Was this translation helpful? Give feedback.
Have a look at the pages linked in the README and the wiki—most pointers come from there.
Check out the performance evaluations for DBLP here and PubChem here.
In general, QLever runs well on modern but affordable raw hardware. Every layer of virtualization costs performance. Don’t overthink it—start with what you have and see how it performs.
What dataset size are you working with?
Start with the defaults and adjust as needed. If you run out of memory for queries, it likely means QLever isn't optimizing that query type effi…