Hello,
I am trying to measure why some of my queries take a long time. I am using
EmbeddedSolrServer and with logging statements before and
after the EmbeddedSolrServer.query(SolrQuery) function, I have found the
time to be around 16s. I added the debugQuery=true and the timing component
for this reads as following:
*
timing:{time=2438.0,prepare={time=0.0,org.apache.solr.handler.component.QueryComponent={time=0.0},org.apache.solr.handler.component.FacetComponent={time=0.0},org.apache.solr.handler.component.MoreLikeThisComponent={time=0.0},org.apache.solr.handler.component.HighlightComponent={time=0.0},org.apache.solr.handler.component.DebugComponent={time=0.0}},process={time=2438.0,org.apache.solr.handler.component.QueryComponent={time=2438.0},org.apache.solr.handler.component.FacetComponent={time=0.0},org.apache.solr.handler.component.MoreLikeThisComponent={time=0.0},org.apache.solr.handler.component.HighlightComponent={time=0.0},org.apache.solr.handler.component.DebugComponent={time=0.0}}}
*
As you can see, this shows only 2.4s being used by the query. I can't seem
to figure out where the rest of the time is being spent. This is within my
office intranet and I don't think the request-response time over the wire
will cause significant overhead. So my question : is the timing information
presented here comprehensive or are there more time consuming operations
that are not represented here ? I guess GC pause times could be one answer
(I hope not !).... Also, the above result was for a faceted query. I can't
understand why the FacetComponent would be zero. Any thoughts ?
Rahul
