Re: Confusing debug=timing parameter

2016-12-19 Thread Walter Underwood
One other thing. How many results are being requested? That is, what is the “rows” parameter? Time includes query time. It does not include networking time for sending 10,000 huge results to the client. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) >

Re: Confusing debug=timing parameter

2016-12-19 Thread Chris Hostetter
SG: IIRC, when doing a distributed/cloud search, the timing info returned for each stage is the *cummulative* time spent on that stage in all shards -- so if you have 4 shards, the "process" time reported could be 4x as much as the actual process time spent. The QTime reported back (in a dist

Re: Confusing debug=timing parameter

2016-12-18 Thread S G
Thank you Furkan. I am still a little confused. So I will shorten the response and post only the relevant pieces for easier understanding. "responseHeader": { "status": 0, "QTime": 2978 } "response": { "numFound": 1565135270, }, "debug": { "timing": { "time": 19320,

Re: Confusing debug=timing parameter

2016-12-18 Thread Furkan KAMACI
Hi, Let me explain you *time* *parameters in Solr*: *Timing* parameter of debug returns information about how long the query took to process. *Query time* shows information of how long did it take in Solr to get the search results. It doesn't include reading bits from disk, etc. Also, there is