The answer is not clear.

Suppose I have following query and I want 10 records.
Condition1 AND Condition2 AND Condition3

As per my understanding Lucene will first evaluate all conditions
separately and then merge the Documents as per AND/OR clauses.
At last it will return me 10 records.

So, if I add one more condition, then it will add to search time and merge
time and hence increase latency, which results in decreased throughput.


Also, what is the search performance benchmark against Lucene version?


Regards
Rajnish







On Tuesday 3 January 2017, Michael Wilkowski <m...@silenteight.com> wrote:

> My guess: more conditions = less documents to score and sort to return.
>
> On Mon, Jan 2, 2017 at 7:23 PM, Rajnish kamboj <rajnishk7.i...@gmail.com>
> wrote:
>
> > Hi
> >
> > Is there any Lucene performance benchmark against certain set of data?
> > [i.e Is there any stats for search throughput which Lucene can provide
> for
> > a certain data?]
> >
> > Search throughput Example:
> > Max. 200 TPS for 50K data on Lucene 5.3.1 on RHEL version x (with SSD)
> > Max. 150 TPS for 100K data on Lucene 5.3.1 on RHEL version x (with SSD)
> > Max. 300 TPS for 50K data on Lucene 6.0.0 on RHEL version x (with SSD)
> > etc.
> >
> > Also, does the index size matters for search throughput?
> >
> > Our observation:
> > When we increase the data size (hence index size) the search throughput
> > decreases.
> > When we add more AND conditions, the search throughput increases. Why?
> > Ideally if we add more conditions then the Lucene should have more work
> to
> > do (including merging) and the throughput should decrease but the
> > throughput increases?
> >
> >
> > Regards
> > Rajnish
> >
>

Reply via email to