Hi Everyone,
On 9/6/24 11:46 AM, Samuel Klein 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 costsGiven 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
Is there a place where SPARQL URLs for the various benchmarks are collated? SPARQL makes transparency dead easy via SPARQL URLs.
I am also very interested in what "numerous hurdles" is supposed to imply regarding Virtuoso when its installation boils downs to;
1. Run an installer (you don't even need to build its Open Source Edition binary).
2. Start server
3. Start interacting with SPARQL via the instance endpoint.