You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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:
Many of the examples are surprisingly slow. The
linestring
example takes half a second. The firstpolygon
example takes 4.8 seconds. The second one takes 13 seconds. The next two fail entirely. Themultipolygon
andgeometrycollection
examples takes 21 seconds....The
multilinestring
andenvelope
examples put the 2GB node into a GC death spiral.The text was updated successfully, but these errors were encountered: