Hi florin,
I am using below.
1) fq={!collapse field=parentglusrid}
2) expand.rows=4
3) expand=true
Size of index is around 100GB.
Solr version is 6.5
On Mon, Mar 8, 2021 at 1:46 PM Florin Babes <babesflo...@gmail.com> wrote:
> Hello,
> First let's call the field you collapse on group_field
> If group_field has a high cardinality you should make group_field null for
> those documents that have a unique group_field and set nullPolicy=expand.
> By doing that solr will use less memory for it's internal maps (so faster
> gc) and the head selecting will be faster.
> What is your head selecting strategy? Can you share your fq which you use
> for collapsing?
>
> Thanks,
> Florin Babes
>
>
>
> În lun., 8 mar. 2021 la 06:44, Parshant Kumar
> <parshant.ku...@indiamart.com.invalid> a scris:
>
> > anyone please help
> >
> > On Wed, Mar 3, 2021 at 4:55 PM Parshant Kumar <
> > parshant.ku...@indiamart.com>
> > wrote:
> >
> > > Hi all,
> > >
> > > We have implemented collapse queries in place of grouped queries on our
> > > production solr. As mentioned in solr documentation collapse queries
> are
> > > recommended in place of grouped queries in terms of performance . But
> > after
> > > switching to collapsed queries from grouped queries response time of
> > > queries have increased. This is unexpected behaviour, the response time
> > > should have been improved but results are opposites.
> > > Please someone help why response time is increased for collapsed
> queries.
> > >
> > > Thanks
> > > Parshant Kumar
> > >
> >
> > --
> >
> >
>
--
