Hi Denny,

I believe virtuoso opensource can run a work load at wikidata at 10x the current scale on commodity hardware. My experience as doing the work on UniProt sparql endpoint says that is very possible.

While UniProt is less dynamic it is much more time boxed in it's release cycle.


Regards,
Jerven


SIB logo
Jerven Tjalling Bolleman
Principal Software Engineer
SIB | Swiss Institute of Bioinformatics
1, rue Michel Servet - CH 1211 Geneva 4 - Switzerland
t +41 22 379 58 85
Jerven.Bolleman@sib.swiss - www.sib.swiss


From: Denny Vrandečić <vrandecic@gmail.com>
Sent: 25 September 2024 07:40
To: Discussion list for the Wikidata project <wikidata@lists.wikimedia.org>
Subject: [Wikidata] Re: [Wikitech-l] Re: [BREAKING CHANGE ANNOUNCEMENT] Wikidata Query Service graph split available in production; scholarly entity queries require migration by March 2025
 
If my memory serves me well, the Open Source version of Virtuoso doesn't have certain scalability features that would be necessary to run a graph as large and dynamic as Wikidata's. Is this information out-of-date?

Cheers,
Denny

On Tue, Sep 24, 2024 at 10:35 PM Kingsley Idehen via Wikidata <wikidata@lists.wikimedia.org> wrote:

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 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


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.

-- 
Regards,

Kingsley Idehen	      
Founder & CEO 
OpenLink Software   
Home Page: http://www.openlinksw.com
Community Support: https://community.openlinksw.com
Weblogs (Blogs):
Company Blog: https://medium.com/openlink-software-blog
Virtuoso Blog: https://medium.com/virtuoso-blog
Data Access Drivers Blog: https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers

Personal Weblogs (Blogs):
Medium Blog: https://medium.com/@kidehen
Legacy Blogs: http://www.openlinksw.com/blog/~kidehen/
              http://kidehen.blogspot.com

Profile Pages:
Pinterest: https://www.pinterest.com/kidehen/
Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen
Twitter: https://twitter.com/kidehen
Google+: https://plus.google.com/+KingsleyIdehen/about
LinkedIn: http://www.linkedin.com/in/kidehen

Web Identities (WebID):
Personal: http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i
        : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this

_______________________________________________
Wikidata mailing list -- wikidata@lists.wikimedia.org
Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/message/2OLO2COIRW5XAVRQRX7VI4ODKTM72X3K/
To unsubscribe send an email to wikidata-leave@lists.wikimedia.org