For my test case it's the same every time. In the "real" query it will change every time, but I planned to not cache this filter and have a less granular date filter in the bool filter that would be cached. However while debugging I noticed slowness with the date range filters even while testing with the same value repeatedly. On Jul 29, 2014 10:49 PM, "David Pilato" <da...@pilato.fr> wrote:
> Any chance your filter value changes for every call? > Or are you using exactly the same value each time? > > -- > David ;-) > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > > Le 30 juil. 2014 à 05:03, Kireet Reddy <kir...@feedly.com> a écrit : > > One of my queries has been consistently taking 500ms-1s and I can't figure > out why. Here is the query > <https://gist.github.com/anonymous/d98fb2c46d9a7755e882> (it looks a bit > strange as I have removed things that didn't seem to affect execution > time). When I remove the range filter, the query consistently takes < 10ms. > The query itself only results 1 hit with or without the range filter, so I > am not sure why simply including this filter adds so much time. My nodes > are not experiencing any filter cache evictions. I also tried moving it to > the bool section with no luck. Changing execution to "fielddata" does > improve execution time to < 10ms though. Since I am sorting on the same > field, I suppose this should be fine. But I would like to understand why > the slowdown occurs. The published field is a date type and has eager field > data loading enabled. > > Thanks > Kireet > > > -- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/994f4700-7a52-4db4-a2a7-d252732517bd%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/994f4700-7a52-4db4-a2a7-d252732517bd%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/elasticsearch/N0z5eZRPO2A/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/CE4B26B8-5837-46C5-9E89-2AFBADED9BB6%40pilato.fr > <https://groups.google.com/d/msgid/elasticsearch/CE4B26B8-5837-46C5-9E89-2AFBADED9BB6%40pilato.fr?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CACkKG4iMwtd-i_NE2mWM6Ce3WeEGM_cpsJXzFsdOUc5n_PTU-A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
