Looking to alternatives to Blazegraph (Qlever being one of those) is definitely on our list of things to do once we have completed our current project of splitting the graph!

On Fri, 6 Sept 2024 at 17:47, Samuel Klein <meta.sj@gmail.com> wrote:
On Fri, Sep 6, 2024 at 4:52 AM Luca Martinelli [Sannita@WMF] <sannita@wikimedia.org> wrote:
no "magic solution" exists, each comes with its load of problems and costs  

Given the reload speed, approach to more continuous updating, and recent performance  benchmarks from the page you referenced, QLever seems pretty magical.  [it was less so when the initial evaluation of backend alternatives came out]  It's also cheap enough to run at home that some people are scratching their own itch now when they have queries that time out on WDQS, as Peter highlights.

Iterating on that benchmark until no one has any concerns with its applicability to our use case seems like a short-term high-return investment.    SJ

 
Hope this helps.
L.

[2] https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_update/WDQS_backend_alternatives
_______________________________________________
Wikidata mailing list -- wikidata@lists.wikimedia.org
Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/message/OWFYNJACO37SCOBC47JLPDHCO52MFRQD/
To unsubscribe send an email to wikidata-leave@lists.wikimedia.org


--
Guillaume Lederrey (he/him)
Engineering Manager
Wikimedia Foundation