[Wikidata-bugs] [Maniphest] T206561: Evaluate Virtuoso as alternative to Blazegraph

Gehel closed this task as "Resolved". Gehel claimed this task. Gehel added a comment. Evaluation is documented in https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_update/WDQS_backend_alternatives TASK DETAIL https://phabricator.wikimedia.org/T206561 EMAIL

[Wikidata-bugs] [Maniphest] T206561: Evaluate Virtuoso as alternative to Blazegraph

MPhamWMF raised the priority of this task from "Low" to "High". TASK DETAIL https://phabricator.wikimedia.org/T206561 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: MPhamWMF Cc: Bugreporter, Hannah_Bast, KingsleyIdehen, So9q, TallTed, Sj, Jerven,

[Wikidata-bugs] [Maniphest] T206561: Evaluate Virtuoso as alternative to Blazegraph

Bugreporter added a comment. Note some queries may not run correctly in virtuoso - see T303263: Stable snapshot and test queries to ensure the correctness of query results for detail TASK DETAIL https://phabricator.wikimedia.org/T206561 EMAIL

[Wikidata-bugs] [Maniphest] T206561: Evaluate Virtuoso as alternative to Blazegraph

Hannah_Bast added a comment. I agree with Kingsley that you don't need a distributed SPARQL engine when the knowledge graph fits on a single machine and will do so also in the future. Which is clearly the case for Wikidata, since it's even the case for the ten times larger UniProt (which at

[Wikidata-bugs] [Maniphest] T206561: Evaluate Virtuoso as alternative to Blazegraph

So9q added a comment. @KingsleyIdehen maybe you can help shed some light on the questions about Virtuoso here? > Data representation > Geographical triples specifying coordinate system can not be loaded: "http://www.wikidata.org/entity/Q405 Point(-49.2

[Wikidata-bugs] [Maniphest] T206561: Evaluate Virtuoso as alternative to Blazegraph

So9q added a comment. In T206561#7309790 , @KingsleyIdehen wrote: > In T206561#7304519 , @So9q wrote: > >> I took a glance at Virtuoso. >> >> I found nothing about scaling

[Wikidata-bugs] [Maniphest] T206561: Evaluate Virtuoso as alternative to Blazegraph

So9q added a comment. In T206561#4682207 , @Smalyshev wrote: > Unfortunately, since all clustering and replication solutions seem to be non-opensource, we would not be able - at least without either using commercial version or getting

[Wikidata-bugs] [Maniphest] T206561: Evaluate Virtuoso as alternative to Blazegraph

KingsleyIdehen added a comment. In T206561#7304519 , @So9q wrote: > I took a glance at Virtuoso. > > I found nothing about scaling Virtuoso to a cluster (which is IMO what WMF needs because of growing amounts of data and reaching

[Wikidata-bugs] [Maniphest] T206561: Evaluate Virtuoso as alternative to Blazegraph

So9q added a comment. I took a glance at Virtuoso. I found nothing about scaling Virtuoso to a cluster (which is IMO what WMF needs because of growing amounts of data and reaching the limits of what 1 machine can handle) A snippet from WP: "Virtuoso is designed to take advantage

[Wikidata-bugs] [Maniphest] T206561: Evaluate Virtuoso as alternative to Blazegraph

Sj added a comment. @Jerven: these are two great updates, thank you. Is there any more recent presentation you could share? Perhaps you could give a brown bag talk and record it as one :) Working with Kingsley + others @ OpenLink on evaluating this makes a lot of sense. TASK DETAIL

[Wikidata-bugs] [Maniphest] T206561: Evaluate Virtuoso as alternative to Blazegraph

Jerven added a comment. By chance a post on how to load all of wikidata into a virtuoso instance appeared today. TASK DETAIL https://phabricator.wikimedia.org/T206561 EMAIL

[Wikidata-bugs] [Maniphest] T206561: Evaluate Virtuoso as alternative to Blazegraph

Jerven added a comment. I just want to note my experience running sparql.uniprot.org. Which is currently about 10 times the size of wikidata in number of triples. An old but still applicable slide set/video is https://www.youtube.com/watch?v=lSfeYdHfCGQ. We also have very large literals

[Wikidata-bugs] [Maniphest] T206561: Evaluate Virtuoso as alternative to Blazegraph

Aklapper changed the task status from "Stalled" to "Open". Aklapper lowered the priority of this task from "Medium" to "Low". Aklapper added a comment. The previous comments don't explain who or what (task?) exactly this task is stalled on ("If a report is waiting for further input (e.g. from