Hi,

Thank you for your answer. Is it something that is somehow theoretically quantifiable, or the only way to quantify the overhead is to prototype and to benchmark?

Regards,

Aurelien

On 28.07.2015 17:15, Uwe Schindler wrote:
It depends on the number of fields. If you search on 3 fields it is
not likely to be a problem (the general use case 3 fields: plain,
stemmed, folded). But if you have like 50 fields, the slow down is
likely very large!

-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de


-----Original Message-----
From: aurelien.mazo...@francelabs.com
[mailto:aurelien.mazo...@francelabs.com]
Sent: Tuesday, July 28, 2015 5:05 PM
To: java-user@lucene.apache.org
Subject: Performance impact of searching across multiple fields

Hi,

I am wondering about the real performance impact of searching across
multiple fields instead of using a catch-all field. I know that Lucene is
optimized to do that and that there are mechanisms to mitigate the
overhead but does anybody know if  there are performance benchmarks
related to this question?

Thanks,

Aurélien


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


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


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

Reply via email to