Thanks darren, I understand it will take longer time before warming up. What I am trying to find out is at the situation where we have no cache, why it will take so long time to complete the query, and what is the bottleneck?
Fx, if I remove all qf, pf fields, the query speed will improve dramatically. Does it indicate a performance hole in boosting part of the code?? Predefined query will impove the speed a lot if the query string or documents that are cached, but it does not improve the speed of a new query. It will still spend the same time to do the scoreing, boosting, filtering etc. And memory is also a problem for big indexes, in my case, I had in total over 100gb indexes in one solr installation. I can't even imagine how solr can handle complex query for 1tb index data in my case. For those customers who unluckily send un-prewarmed query, they will suffer from bad response time, it is not too pleasant anyway. best regards, shen On Tue, Jan 17, 2012 at 3:18 PM, <dar...@ontrenet.com> wrote: > First query will cause the index caches to be warmed up and this is why > the first query takes some time. > > You can prewarm the caches with a query (when solr starts up) of your > choosing in the config file. Google around the SolrWiki on cache/index > warming. > > hth > > > hi, > > > > I had an solr3.3 index of 200,000 documents, all text are stored and the > > total index size is 27gb. > > I used dismax query with over 10 qf and pf boosting field each, plus > > sorting on score and other 2 fields. It took quite a few seconds(5-8) for > > the first time query to return any result(no highlighting is invloved). > > (even slower for phrase query) > > > > My question is, what is the bottle neck of the query speed? lucene query > > part? Scoring? or fill document cache with document content? Can anyone > > answer? > > > > Is there anyway of improving the first time query speed? > > > > thanks in advance, > > shen > > > >
