On Fri, Sep 6, 2024 at 4:52 AM Luca Martinelli [Sannita@WMF] < sann...@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 <https://github.com/ad-freiburg/qlever/wiki/QLever-support-for-SPARQL-1.1-Update>, and recent performance <https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_update/WDQS_backend_alternatives#A_Report_on_Using_QLever> benchmarks <https://github.com/ad-freiburg/qlever/wiki/QLever-performance-evaluation-and-comparison-to-other-SPARQL-engines> 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 >
_______________________________________________ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
