Hi Peter,

This isn't perfect as there's a race condition in the Blazegraph code if the query runs "too fast" [1], but if I understood the question correctly, would something like the following help?

curl https://query.wikidata.org/sparql \ -d "query= SELECT * WHERE { ?s ?p ?o } limit 1000" \ -d "explain" -o ~/explainSimple.html

( equivalent GET URL: https://query.wikidata.org/sparql?explain&query=select%20*%20where%20%7B... )

curl https://query.wikidata.org/sparql \ -d "query= SELECT * WHERE { ?s ?p ?o } limit 1000" \ -d "explain=details" -o ~/explainDetails.html

( equivalent GET URL: https://query.wikidata.org/sparql?explain=details&query=select%20*%20whe... )

-Adam

[1] https://gerrit.wikimedia.org/r/plugins/gitiles/wikidata/query/blazegraph/+/7...

[2] https://github.com/blazegraph/database/wiki/Explain

On Fri, Sep 6, 2024 at 10:11 AM Peter F. Patel-Schneider < pfpschneider@gmail.com> wrote:

Is there a way to get the Wikidata Query Service to report the total time taken to evaluate a query? This would be better than estimating the time from the elapsed time between a request and the beginning of a response.

peter _______________________________________________ Wikidata mailing list -- wikidata@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/mes... To unsubscribe send an email to wikidata-leave@lists.wikimedia.org