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
The current implementation of GeoIndex wraps an IOBTree object containing all the gometries in the index. While it works fine for searching, it can produce a sort of memory leak when loading data.
I have a big amount of georeferenced data (1.2M) and an ETL procedure to load them all one shot.
Unfortunately the memory consumption grows up to 50GB and the process exits because killed.
I tried to commit the transaction and the subtransaction in batches, but did not help.
Any suggestions?
The text was updated successfully, but these errors were encountered:
The current implementation of GeoIndex wraps an IOBTree object containing all the gometries in the index. While it works fine for searching, it can produce a sort of memory leak when loading data.
I have a big amount of georeferenced data (1.2M) and an ETL procedure to load them all one shot.
Unfortunately the memory consumption grows up to 50GB and the process exits because killed.
I tried to commit the transaction and the subtransaction in batches, but did not help.
Any suggestions?
The text was updated successfully, but these errors were encountered: