On 5/17/2020 4:18 PM, Dominique Bejean wrote:
I was not thinking that queries using facet with fields with high number of unique value but with low hits count can be the origin of this problem.
Performance for most things does not depend on numFound (hit count) or the rows parameter. The number of terms in the field and the total number of documents in the index matters a lot more.
If you do facets or grouping on a field with 750K unique terms, it's going to be very slow and require a LOT of memory. I would not be surprised to see it require more than 4GB. These features are designed to work best with fields that have a relatively small number of possible values.
Thanks, Shawn
