Adrian,
Thanks for that. I had a feeling that that might be the case.
Any tips on improving aggregation performance. I'm working with a 20 shard
index that is loaded on a 20 node cluster. Geohash grid aggregations on
the entire data set (with the size set to unlimited - a requirement) can
Just as a thought, would setting geohash = true or geohash_prefix = true at
index time improve performance?
On Monday, January 5, 2015 7:20:32 AM UTC-5, Elliott Bradshaw wrote:
Adrian,
Thanks for that. I had a feeling that that might be the case.
Any tips on improving aggregation
No it wouldn't. I don't have ideas about how to improve performance, are
you running only a geohash grid aggregation or do you also have sub
aggregations? Also 1 million buckets is a lot, if it would work for you to
decrease the value of the precision parameter, this could help with
performance.
I am only running a geohash grid aggregation. I reduce the precision
parameter as much as I can in each case. Any guesses on where most of the
time is being spent? I could dig through the source...
On Monday, January 5, 2015 9:49:01 AM UTC-5, Adrien Grand wrote:
No it wouldn't. I don't
Hi,
I'm currently working on a project that visualizes geospatial data in
Elasticsearch. One of the things I am doing is generating heatmaps with
the geohash grid aggregation. I would like to take this to the extreme
case of gridding down to the individual pixel level to display raster
Hi Eliott,
The overhead of computing the doc counts is actually low, I don't think you
should worry about it.
On Tue, Dec 30, 2014 at 5:12 PM, Elliott Bradshaw ebradsh...@gmail.com
wrote:
Hi,
I'm currently working on a project that visualizes geospatial data in
Elasticsearch. One of the
