lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <>
Subject Re: Optimize facets when actually single valued?
Date Sun, 11 Nov 2012 13:04:01 GMT
You have to provide more details. How many unique values are there in the
field in question? What's the query you're using? Are you sure other parts
of the query aren't the culprit? What Solr version are you using?

Please review:


On Sat, Nov 10, 2012 at 9:41 PM, Jimmy Sélamy <> wrote:

> **
> Im having perfomance issues with facet on multivalued field with an index
> over 20Million documents.
> And when doing faceting search on multivalued field the QTIME is
> unacceptable for my application because it can take up to 6000ms.
> Ive put the facet.method to enum! Which increased my performance to the
> time i just mentionned! Its still not acceptable.
> Is there any suggestions ?
> Envoyé avec BlackBerry sur le réseau mobile de Vidéotron
> ------------------------------
> *From: * Robert Muir <>
> *Date: *Sat, 10 Nov 2012 21:33:47 -0500
> *To: *<>
> *ReplyTo: *
> *Subject: *Optimize facets when actually single valued?
> I am guessing at times people are lazy about schema definition. But, I
> think with lucene 4 stats we can detect if a field is actually single
> valued... Something like terms.size == terms.doccount == terms.sumdocfreq.
> I have to think about it a bit, maybe its even simpler than this? Anyway,
> this couple be used instead of actual schema def to just build a fieldcache
> instead of uninverted field I think... Should be a simple opto but maybe
> potent...

View raw message