lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Wilkowski ...@silenteight.com>
Subject Re: Lucene performance benchmark | search throughput
Date Tue, 03 Jan 2017 08:15:28 GMT
My guess: more conditions = less documents to score and sort to return.

On Mon, Jan 2, 2017 at 7:23 PM, Rajnish kamboj <rajnishk7.info@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
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message