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
When processing many inputs that don't all fit in node's default heap size, rather than just crash with an out-of-memory error it would be better to read in a subset of the inputs, process those, then read in another set of inputs, process those, etc.
The text was updated successfully, but these errors were encountered:
Turns out on my primary use case (subtracting water areas from geopolitical shapes) this only results in about a 10% improvement in memory usage, because the water areas aren't overlapping.
As such I'll leave this tagged on a branch but won't be merging it into master.
When processing many inputs that don't all fit in node's default heap size, rather than just crash with an out-of-memory error it would be better to read in a subset of the inputs, process those, then read in another set of inputs, process those, etc.
The text was updated successfully, but these errors were encountered: