lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Hammond" <>
Subject RE: Slow response
Date Thu, 06 Sep 2007 22:16:15 GMT
Thank-you for your response, this does shed some light on the subject.
Our basic question was why were we seeing slower responses the smaller
our result set got. 

Currently we are searching about 1.2 million documents with the source
document about 2KB, but we do duplicate some of the data. I bumped up my
filterCache to 5 million and the 2nd search I did for an non-indexed
term came back in 2.1 seconds so that is much improved. I am a little
concerned about having this value so high but this is our problem and we
will play with it. 

I do have a few follow-up questions. First, in regards to the
filterCache once a single search has been done and facets requested, as
long as new facets aren't requested and the size is large enough then
the filters will remain in the cache, correct?

Also, you mention that faceting is more a "function of the number of the
number of terms in the field". The 2 fields causing our problems are
Authors and Subjects. If we divided up the data that made these facets
into more specific fields (Primary author, secondary author, etc.) would
this perform better? So the number of facet fields would increase but
the unique terms for a given facet should be less.

Thanks again for all your help.


-----Original Message-----
From: [] On Behalf Of Yonik
Sent: Thursday, September 06, 2007 4:17 PM
Subject: Re: Slow response

On 9/6/07, Aaron Hammond <> wrote:
> I am pretty new to Solr and this is my first post to this list so
> forgive me if I make any glaring errors.
> Here's my problem. When I do a search using the Solr admin interface
> a term that I know does not exist in my index the QTime is about 1ms.
> However, if I add facets to the search the response takes more than 20
> seconds (and sometimes longer) to return. Here is the slow URL -

Faceting on multi-value fields is more a function of the number of
terms in the field (and their distribution) rather than the number of
hits for a query.  That said, perhaps faceting should be able to bail
out if there are no hits.

Is your question more about why faceting takes so long in general, or
why it takes so long if there are no results?  If you haven't, try
optimizing your index for facet faceting in general.  How many docs do
you have in your index?

As a side note, the way multi-valued faceting currently works, it's
actually normally faster if the query returns a large number of hits.


View raw message