lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jimmy Sélamy" <jym...@gmail.com>
Subject Re: Optimize facets when actually single valued?
Date Sun, 11 Nov 2012 02:41:10 GMT
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

-----Original Message-----
From: Robert Muir <rcmuir@gmail.com>
Date: Sat, 10 Nov 2012 21:33:47 
To: <dev@lucene.apache.org>
Reply-To: dev@lucene.apache.org
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...

Mime
View raw message