In both setups, we are reading in batches of 50k and each batch taking
Setup1  : approx 7 seconds and for completing all batches of total 10 lakh
results takes 1 to 2 minutes.
Setup2 : approx 2-3 minutes and for completing all batches of total 10 lakh
results  takes 114 minutes.

We tried other batch size also 10k, 1lakh but no gain in total time taken
in Setup2.

Thanks
Naresh


On Sun, Jan 18, 2015 at 6:45 AM, Andrew Butkus <
andrew.but...@c6-intelligence.com> wrote:

> &shard.info=true
>
> Sent from my iPhone
>
> > On 17 Jan 2015, at 04:23, Naresh Yadav <nyadav....@gmail.com> wrote:
> >
> > Hi all,
> >
> > We have single solr index with 3 fixed fields(on of field is tokenized
> with
> > space) and rest dynamic fields(string fields in range of 10-20).
> >
> > Current size of index is 2 GB with around 12 lakh docs and solr
> > nodes are of 4 core, 16 gb ram linux machines.
> >
> > Writes performance is good then we tested one read query(In select query
> we
> > are applying filter criteria on tokenized field & reading only score
> field,
> > no grouping/faceting) in two setups :
> >
> > *Setup1 : *Single Node Cloud with shards=1, replication=1
> > In this setup whole 12 lakh docs are on same machine. Our filter query
> > reading
> > around 10 lakh docs with only score field is taking *1 minutes*.
> >
> > *Setup2 : *Two Node Cloud with shards=2, replication=1
> > In this setup whole 6 lakh docs on node1 and 6 lakh on node2. Our same
> > filter query reading around 10 lakh docs with only score field is taking
> *114
> > minutes.*
> >
> > Please guide us what can be possible reasons of degradation of
> > performance after sharding of index. How can we check where solr server
> > is taking time to return results.
> >
> > Thanks
> > Naresh
>

Reply via email to