Thanks for yours quick feedback.
The problem happens by the customer and we trying to simulate it on our
environments in order to figure out which part of the query is slow.
I add some informations:
- the facet *dimension* is composed by *2 categories* (for example
"/cat1/cat2") and the *s
Hi Simona,
In addition to Ericks' questions:
Are you talking about *search* time or facet-collection time? And how many
results are in your result set?
I have some experience with collecting facets from large results set, these
are typically slow (as they have to retrieve all the relevant facet
Message-
> > From: Erick Erickson [mailto:erickerick...@gmail.com]
> > Sent: Friday, February 26, 2016 8:22 AM
> > To: java-user
> > Subject: Re: Lucene Facets performance problems (version 4.7.2)
> >
> > You haven't given us much to go on. What is the cardina
sage-
> From: Erick Erickson [mailto:erickerick...@gmail.com]
> Sent: Friday, February 26, 2016 8:22 AM
> To: java-user
> Subject: Re: Lucene Facets performance problems (version 4.7.2)
>
> You haven't given us much to go on. What is the cardinality of the fields
> you
You haven't given us much to go on. What is the cardinality of the fields
you're faceting on? What does your query look like? How are you measuring
time? What is the output if you add &debug=true?
In short, your question is far too vague to give any meaningful
information, there could be any of a
Hi all,
we use Lucene *Facet* library version* 4.7.2.*
We have an *index* with *45 millions *of documents (size about 15 GB) and
a *taxonomy* index with *57* millions of documents (size about 2 GB).
The total *facet search* time achieve *15 seconds*!
Is it possible to improve this time? Is the