lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shalin Shekhar Mangar <>
Subject Re: Improvising solr queries
Date Mon, 04 Jan 2010 13:46:16 GMT
On Mon, Jan 4, 2010 at 6:39 PM, dipti khullar <>wrote:

> We have tried out various configurations settings to improvise the
> performance of the site which is majorly using Solr but still the response
> time remains about 4-5 reqs/sec. We also did some performance tests on Solr
> 1.4 but still there is a very minute improvement in performance. Currently
> we are using Solr 1.3.

That is too slow.

We need more information on your setup before we can help. What kind of
hardware you are using? Which OS/JVM? How much memory have you allocated to
the JVM?

What does your solrconfig look like? How many documents are there in your
index? What is the size of index on disk? What are the field types of the
fields you are searching on? Do you do highlighting on large fields? Can you
paste the cache section on the statistics page of your Solr dashboard
(preferably, just after a peak load)? How frequently is your index changed
(i.e. how frequently do you commit)?

I'd recommend an upgrade to Solr 1.4 anyway since it has major performance

> So our last resort remains, improvising the queries. We are using SolrJ -
> CommonsHttpSolrServer
Actually that is one of the first things that you should look at.

> We guys are trying to tune up Solr Queries being used in our project.
> Following sample query takes about 6 secs to execute under normal traffic.
> At peak hours this often increases to 10-15 secs.
> sitename:XYZ OR sitename:"All Sites") AND (localeid:1237400589415) AND
> ((assettype:Gallery))  AND (rbcategory:"ABC XYZ" ) AND (startdate:[* TO
> 2009-12-07T23:59:00Z] AND enddate:[2009-12-07T00:00:00Z TO
> *])&rows=9&start=63&sort=date
> desc&facet=true&facet.field=assettype&facet.mincount=1
> Similar to this query we have several much complex queries supporting all
> major landing pages of our application.
> Just want to confirm that whether anyone can identify any major flaws or
> issues in the sample query?
Most of those AND conditions can be separate filter queries. Filter queries
can be cached separately and can therefore be re-used. See

Shalin Shekhar Mangar.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message