-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Closed
Labels
:Analytics/GeoIndexing, search aggregations of geo points and shapesIndexing, search aggregations of geo points and shapes>bug
Description
I was converting the examples on the geo-shape page to // CONSOLE so they are automatically tested and noticed that they use a crazy amount of memory. We should certainly fix the docs, but we really need to prevent these from using so much memory like we do with aggregations or the NFA -> DFA construction.
To reproduce, setup the index like the documentation does:
PUT /example
{
"mappings": {
"doc": {
"properties": {
"location": {
"type": "geo_shape",
"tree": "quadtree",
"precision": "1m"
}
}
}
}
}
Many of the examples are surprisingly slow. The linestring example takes half a second. The first polygon example takes 4.8 seconds. The second one takes 13 seconds. The next two fail entirely. The multipolygon and geometrycollection examples takes 21 seconds....
Themultilinestring and envelope examples put the 2GB node into a GC death spiral.
Metadata
Metadata
Assignees
Labels
:Analytics/GeoIndexing, search aggregations of geo points and shapesIndexing, search aggregations of geo points and shapes>bug