Hi Stas,
Regarding your guess that network connectivity could cause my problem: I
got the 55sec time while in my office, connected via an Ethernet cable
to the university network. This is more or less directly wired up to the
backbone of the Internet, so bandwidth cannot be the issue here.
I now got better times for that query on Chrome (my first try was on
Firefox). Maybe the different Javascript speeds are the main issue here.
However, most other queries I try still time out or at least don't give
any results for some reason, even on Chrome.
Best,
Markus
On 21.12.2016 22:07, Stas Malyshev wrote:
Hi!
Also, there should be some way of doing queries
that don't run on WDQS
already, i.e., there must be something that times out now but can be
done with ldf in a reasonable time [1]. Or are federated queries the
main goal here? (that's still useful, but I hope that WDQS will also
support a whitelisted set of external endpoint at some time)
Yes, the plan is to have a whitelist of SPARQL endpoints for which we
allow federation queries. I was going to post about it in January when
everybody's back from vacations :)
The use case for LDF is both running long queries and federation. The
first use case of course would benefit from good SPARQL engine running
on a machine with decent connectivity. So server-side JS or Java should
probably fare better.