It¹s not just FacetComponent, here¹s the original feature ticket for timeAllowed: https://issues.apache.org/jira/browse/SOLR-502
As I read it, timeAllowed only limits the time spent actually getting documents, not the time spent figuring out what data to get or how. I think that means the primary use-case is serving as a guard against excessive paging. On 4/30/14, 4:49 AM, "Mikhail Khludnev" <mkhlud...@griddynamics.com> wrote: >On Wed, Apr 30, 2014 at 2:16 PM, Aman Tandon ><amantandon...@gmail.com>wrote: > >> <lst name="query"> <double >> name="time">3337.0</double> </lst> <lst name="facet"> >> <double name="time">6739.0</double> </lst> >> > >Most time is spent in facet counting. FacetComponent doesn't checks >timeAllowed right now. You can try to experiment with facet.method=enum or >even with https://issues.apache.org/jira/browse/SOLR-5725 or try to >distribute search with SolrCloud. AFAIK, you can't employ threads to speed >up multivalue facets. > >-- >Sincerely yours >Mikhail Khludnev >Principal Engineer, >Grid Dynamics > ><http://www.griddynamics.com> > <mkhlud...@griddynamics.com>
