Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory consumption #2

Open
marfago opened this issue Jul 6, 2015 · 0 comments
Open

Memory consumption #2

marfago opened this issue Jul 6, 2015 · 0 comments

Comments

@marfago
Copy link

marfago commented Jul 6, 2015

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant