KingsleyIdehen added a comment.
A few things:
1. This behavior is configurable i.e., we just have a restrictive timeout
associated with the current public instance
2. We could also include HTML-level messaging to complement the HTTP-level
messaging
This feature is the result
KingsleyIdehen added a comment.
That's a consequence of the "Anytime Query" feature in Virtuoso that provides
partial solutions in situations where a query cannot be completed within a
specific timeframe. This timeframe takes the form of a configurable timeout,
and is an critic
KingsleyIdehen added a comment.
For the record.
At the time of our first rendezvous re Wikidata hosting, handling 20 billion+
triples would have typically required our Cluster Edition (a Commercial Only
offering). That was the deal-breaker back at the time of initial Blazegraph
KingsleyIdehen added a comment.
In T206561#7304519 <https://phabricator.wikimedia.org/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 da
