Re: Performance of stats=true={!cardinality=1.0}fl
On Wed, 2016-01-06 at 12:39 +0530, Modassar Ather wrote: > *q=fl1:net*=fl=50=true={!cardinality=1.0}fl* > is returning cardinality around 15 million. It is taking around 4 minutes. Is this a single shard or multiple? Anyway, you might have better luck trying the 'unique' request in JSON faceting: https://cwiki.apache.org/confluence/display/solr/Faceted+Search - Toke Eskildsen, State and University Library, Denmark
Re: Performance of stats=true={!cardinality=1.0}fl
Hi, An input will be helpful. Thanks, Modassar On Wed, Jan 6, 2016 at 12:39 PM, Modassar Atherwrote: > Hi, > > > *q=fl1:net*=fl=50=true={!cardinality=1.0}fl* > is returning cardinality around 15 million. It is taking around 4 minutes. > Similar response time is seen with different queries which yields high > cardinality. Kindly note that the cardinality=1.0 is the desired goal. > Here in the above example the fl1 is a text field whereas fl is a docValue > enabled non-stroed, non-indexed field. > Kindly let me know if such response time is expected or I am missing > something about this feature in my query. > > Thanks, > Modassar >
Re: Performance of stats=true={!cardinality=1.0}fl
Hi Toke, Is this a single shard or multiple? It is 12 shard cluster without replicas and has around 90+ GB on each shard. Thanks for sharing the link. I will look into that. Regards, Modassar On Fri, Jan 8, 2016 at 4:28 PM, Toke Eskildsenwrote: > On Wed, 2016-01-06 at 12:39 +0530, Modassar Ather wrote: > > > *q=fl1:net*=fl=50=true={!cardinality=1.0}fl* > > is returning cardinality around 15 million. It is taking around 4 > minutes. > > Is this a single shard or multiple? > > Anyway, you might have better luck trying the 'unique' request in JSON > faceting: > https://cwiki.apache.org/confluence/display/solr/Faceted+Search > > - Toke Eskildsen, State and University Library, Denmark > > >
Performance of stats=true={!cardinality=1.0}fl
Hi, *q=fl1:net*=fl=50=true={!cardinality=1.0}fl* is returning cardinality around 15 million. It is taking around 4 minutes. Similar response time is seen with different queries which yields high cardinality. Kindly note that the cardinality=1.0 is the desired goal. Here in the above example the fl1 is a text field whereas fl is a docValue enabled non-stroed, non-indexed field. Kindly let me know if such response time is expected or I am missing something about this feature in my query. Thanks, Modassar