Performance questions

Elastic Stack Elasticsearch
1

After reading this blog-post http://euphonious-intuition.com/2013/02/five-things-i-learned-from-elasticsearch-training/ I have two questions, I hope someone can answer.

  1. when using match all and several filter (no query) is the bool filter still faster?
  2. one filter of mine selects all data of today with gte: "now/d" would setting an upper and lower timestamp increase the performance?

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

2
  1. If you are doing term and a range filter you're better off with Bool. If
    you're doing a range filter and a geo filter and a query filter you could
    see slightly better performance with an And. When in doubt, use bool.
  2. If "now/d" is day granularity instead of being down to the second, then
    having a single gte is a little faster. The point of the optimization is to
    build the filter so that it stays the same over multiple invocations. Under
    some circumstances you may also benefit from chaining range filters inside
    of a Bool filter. For example, you may filter our documents for *last 7 days
  • then apply a last hour filter. That approach will yield better
    results for very large dataset if you expect to run the same query and just
    page backwards one hour at a time. But if your dataset is relatively small,
    having an intermediate range filter will slow down your query a little.

On Wednesday, April 24, 2013 2:03:23 PM UTC-7, Valentin wrote:

After reading this blog-post
http://euphonious-intuition.com/2013/02/five-things-i-learned-from-elasticsearch-training/I have two questions, I hope someone can answer.

  1. when using match all and several filter (no query) is the bool filter
    still faster?
  2. one filter of mine selects all data of today with gte: "now/d" would
    setting an upper and lower timestamp increase the performance?

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

3

Thanks. That info actually helps a lot!

On Wednesday, April 24, 2013 11:33:58 PM UTC+2, Taras Shkvarchuk wrote:

  1. If you are doing term and a range filter you're better off with Bool.
    If you're doing a range filter and a geo filter and a query filter you
    could see slightly better performance with an And. When in doubt, use bool.
  2. If "now/d" is day granularity instead of being down to the second, then
    having a single gte is a little faster. The point of the optimization is to
    build the filter so that it stays the same over multiple invocations. Under
    some circumstances you may also benefit from chaining range filters inside
    of a Bool filter. For example, you may filter our documents for last 7
    days     then apply a last hour filter. That approach will yield better
    results for very large dataset if you expect to run the same query and just
    page backwards one hour at a time. But if your dataset is relatively small,
    having an intermediate range filter will slow down your query a little.

On Wednesday, April 24, 2013 2:03:23 PM UTC-7, Valentin wrote:

After reading this blog-post
http://euphonious-intuition.com/2013/02/five-things-i-learned-from-elasticsearch-training/I have two questions, I hope someone can answer.

  1. when using match all and several filter (no query) is the bool filter
    still faster?
  2. one filter of mine selects all data of today with gte: "now/d" would
    setting an upper and lower timestamp increase the performance?

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.