Solr and Lucene are very efficient at basic ranking and retrieval. Sorting and faceted search take more CPU.
Most of your speed improvement will come from caching, so set aside some time for cache tuning. You need real query logs for that. wunder On 2/18/09 7:31 AM, "Sean Timm" <tim...@aol.com> wrote: > This page gives lots of performance pointers. > > http://wiki.apache.org/solr/SolrPerformanceFactors > > -Sean > > Jana, Kumar Raja wrote: >> Thanks Sean. That clears up the timer concept. >> >> Is there any other way through which I can make sure that the server >> time is not wasted? >> >> -----Original Message----- >> From: Sean Timm [mailto:tim...@aol.com] >> Sent: Wednesday, February 18, 2009 1:00 AM >> To: solr-user@lucene.apache.org >> Subject: Re: Query regarding setTimeAllowed(Integer) and >> setRows(Integer) >> >> Jana, Kumar Raja wrote: >> >>> 2. If I set SolrQuery.setTimeAllowed(2000) Will this kill query >>> processing after 2 secs? (I know this question sounds silly but I just >>> want a confirmation from the experts J >>> >> That is the idea, but only some of the code is within the timer. So, >> there are cases where a query could exceed the timeAllowed specified >> because the bulk of the work for that particular query is not in the >> actual collect, for example, an expensive range query. >> >> -Sean >>
