SPARQL Triplestore and Reasoning Performance #39
Description
"This brings me to SPARQL and inferencing in general. It seems very,
very easy to write a seemingly simple SPARQL query that will lock your
machine. For instance, I have various sub properties of foaf:name
because early Irish is an inflected language, names have different
forms depending on where they are in a sentence. When I search for
foaf:name in a SPARQL query, it never seemed to return and the query
analyser came back with a query plan that was huge. This could have
been just a problem with the Triplestore that I was using (Stardog)
but this seems far easier to do than it is in SQL.
I have been thinking of moving to Marklogic with forward chaining
reasoning and materialisation because I would rather use more disk
than use more CPU. Disk is cheap; CPU is not. Also, this dataset is
meant for an OLAP situation which means that it will change
infrequently but be searched far more often."
https://lists.w3.org/Archives/Public/semantic-web/2018Dec/0088.html