I have an index with around 3 million documents in which there is a single
geo_point field. When performing a geo_distance query I see response times
of around 25,000 ms. After looking more at how geo_distance needs to work
this wasn't surprising but I would have expected geo_bounding_box to be a
lot faster as it has absolute ranges to deal with (as opposed to having to
calculate distance for every document).
But actually it's no faster at all. I see roughly the same response time,
somewhere between 20 and 30 seconds. A "normal" query (i.e. one that does
not have any geo components) takes around 200-500ms on the hardware I am
The reason this is confusing is that a simple range query on a numeric
field has negligible impact on query time. Isn't a bounding box query just
a set of range filters? Really just 2 ranges? (lat range and lon range).
Am I missing something in how bounding box queries work?
I've tried setting the "indexed" type, no change.
The standard response seems to be "get more servers", but I just want to
make sure I'm understanding what's happening here.
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 email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.