lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael McCandless <luc...@mikemccandless.com>
Subject Re: Lucene performance benchmark | search throughput
Date Tue, 03 Jan 2017 11:42:15 GMT
When you add MUST sub-clauses to a BooleanQuery  (AND to the query
parsers) it can make the search run faster because Lucene will take
the most restrictive clause and use that to "drive" the iteration of
matching documents to the other clauses, allowing those other clauses
to iterate much faster than they would otherwise require if they were
not AND'd.

Mike McCandless

http://blog.mikemccandless.com


On Tue, Jan 3, 2017 at 6:33 AM, Rajnish kamboj <rajnishk7.info@gmail.com> wrote:
> 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 <mw@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.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
>> >
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


Mime
View raw message