On 18/06/15 10:34, Neubert, Joachim wrote:
The culprit for the long execution time on the remote server seems to
be the SERVICE clause. Even when it points to an in-memory endpoint
on the same server, execution took more than 400 sec. After loading
the very same data into a named GRAPH on the
...@apache.org]
Gesendet: Mittwoch, 17. Juni 2015 16:30
An: users@jena.apache.org
Betreff: Re: AW: s-query on remote endpoint
On 17/06/15 15:12, Neubert, Joachim wrote:
An follow-up question: Is a
SERVICE http://localhost:3030/ds/query { ... }
clause within the query resolved as localhost
When I execute a query with the s-query script, and -service is located on a
remote machine, I can observe that the load on the remote machine is very low,
while on the local machine fuseki consumes 100% of the cpu. The execution takes
a very long time, much more than when I execute s-query on
) are ruby scripts of a somewhat old nature.
Andy
Cheers, Joachim
-Ursprüngliche Nachricht-
Von: Neubert, Joachim [mailto:j.neub...@zbw.eu]
Gesendet: Mittwoch, 17. Juni 2015 12:00
An: 'users@jena.apache.org'
Betreff: s-query on remote endpoint
When I execute a query with the s-query
Nachricht-
Von: Neubert, Joachim [mailto:j.neub...@zbw.eu]
Gesendet: Mittwoch, 17. Juni 2015 12:00
An: 'users@jena.apache.org'
Betreff: s-query on remote endpoint
When I execute a query with the s-query script, and -service is located on a
remote machine, I can observe that the load
