[Wikidata-bugs] [Maniphest] [Commented On] T206560: [Epic] Evaluate alternatives to Blazegraph

2018-10-19 Thread Gehel
Gehel added a comment. A few wishes I have from an operations point of view for any replacement. Those are not necessarily mandatory, but we should evaluate them at some point: ability to scale both read and write load across multiple nodes ability to limit resource consumption to fail

[Wikidata-bugs] [Maniphest] [Commented On] T206560: [Epic] Evaluate alternatives to Blazegraph

2018-10-10 Thread Lucas_Werkmeister_WMDE
Lucas_Werkmeister_WMDE added a comment. I would clarify the requirements to “SPARQL support, including SPARQL Update”. For example, Sage boasts stable response times and general responsiveness, which would be useful for us, but its backing store is HDT, a read-only RDF serialization format: since