roting "success"
>
> does that make sense?
>
>
>
> : Date: Sat, 17 Dec 2016 08:43:53 -0800
> : From: S G
> : Reply-To: solr-user@lucene.apache.org
> : To: solr-user@lucene.apache.org
> : Subject: Confusing debug=timing parameter
> :
> : Hi,
> :
>
munication overhead, or
client overhead in parsing hte response before proting "success"
does that make sense?
: Date: Sat, 17 Dec 2016 08:43:53 -0800
: From: S G
: Reply-To: solr-user@lucene.apache.org
: To: solr-user@lucene.apache.org
: Subject: Confusing debug=timing parameter
:
:
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,
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
Hi,
I am using Solr 4.10 and its response time for the clients is not very good.
Even though the Solr's plugin/stats shows less than 200 milliseconds,
clients report several seconds in response time.
So I tried using debug-timing parameter from the Solr UI and this is what I
got.
Note how the QTi
