Honestly, with that extensive use of SERVICE feature it clearly would make sense to make use of parallel execution. Never heard of such a query, but sounds like fun.
What is the use-case here? Can you give some insights? Are all of them remote SPARQL services? By the way, did you ever consider or even try on of the existing federated query engines like FedX, ANAPSID, HIBISCUS, etc. ? I'm wondering how those would work (if even scale) with ~100 sources like it looks to be the case in your query? > While using a query with a large number (100+) of remote sparql endpoints, > using the SERVICE keyword for a federated query, I have noticed that Jena > keeps waiting in the queue for slow responses to finish up before > proceeding to the next node. > > Would it not be a good idea to make SERVICE a thread to speed up the > process in the query? > > -- Lorenz Bühmann AKSW group, University of Leipzig Group: http://aksw.org - semantic web research center
