From: Rose B. <ros...@gm...> - 2014-11-13 11:27:44
|
Yes I understand. I need to run multiple queries and report their total query execution time. I know I can do it with bigdata workbench as it does give the total query execution time. But I am running 3000+ queries, so it is becoming impossible for me to note their query execution time individually through bigdata workbench as it runs within the browser. Is there some way: that using CURL I may do the same on command line --- an example will be really helpful. On Thu, Nov 13, 2014 at 4:49 PM, Bryan Thompson <br...@sy...> wrote: > Rose, > > Those are URL query parameters. They are appended onto the end of the > SPARQL endpoint URL. > > http://.../sparql?explain > > If there are multiple URL query parameters then the next one is introduced > with an ampersand &. If there is a value associated with a parameter then > it is ?foo=bar or &foo=bar. This is standard http. > > The explain gives the time to run the query but not the time to send the > results to the client. The client (the workbench) is probably reporting the > total time until the query results are fully materialized on the client. > > The explain output is explained on the performance optimization pages on the > wiki. > > Thanks, > Bryan > > On Thursday, November 13, 2014, Rose Beck <ros...@gm...> wrote: >> >> As stated at http://wiki.bigdata.com/wiki/index.php/NanoSparqlServer >> one can pass "explain" as a parameter to SPARQL query passed in CURL. >> >> curl -X POST http://localhost:8080/bigdata/sparql --data-urlencode >> 'query=SELECT * { ?s ?p ?o } LIMIT 1' -H 'Accept:application/rdf+xml' >> >> However, if I use the following (which works perfectly) well for >> Virtuoso, I get an error: >> curl -X POST http://localhost:8080/bigdata/sparql --data-urlencode >> 'query=explain 'SELECT * { ?s ?p ?o } LIMIT 1'' -H >> 'Accept:application/rdf+xml' >> >> Also "explain" on Bigdata workbench when executed in a browser gives >> elapsed time of the time given below: >> solutions=2, chunks=1, subqueries=0, elapsed=32ms. >> >> Is the elapsed time same as the query execution time -- if not then >> what is the difference? Because on the browser bigdata reports >> different elapsed time as well as query execution time. >> >> >> ------------------------------------------------------------------------------ >> Comprehensive Server Monitoring with Site24x7. >> Monitor 10 servers for $9/Month. >> Get alerted through email, SMS, voice calls or mobile push notifications. >> Take corrective actions from your mobile device. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk >> _______________________________________________ >> Bigdata-developers mailing list >> Big...@li... >> https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > > > -- > ---- > Bryan Thompson > Chief Scientist & Founder > SYSTAP, LLC > 4501 Tower Road > Greensboro, NC 27410 > br...@sy... > http://bigdata.com > http://mapgraph.io > > CONFIDENTIALITY NOTICE: This email and its contents and attachments are for > the sole use of the intended recipient(s) and are confidential or > proprietary to SYSTAP. Any unauthorized review, use, disclosure, > dissemination or copying of this email or its contents or attachments is > prohibited. If you have received this communication in error, please notify > the sender by reply email and permanently delete all copies of the email and > its contents and attachments. > > |