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

User memory issues on immediate retrieval of predict for feature collections #8

Open
grovduck opened this issue Mar 15, 2024 · 0 comments · May be fixed by #9
Open

User memory issues on immediate retrieval of predict for feature collections #8

grovduck opened this issue Mar 15, 2024 · 0 comments · May be fixed by #9
Assignees
Labels
bug Something isn't working

Comments

@grovduck
Copy link
Member

When running RawClassifer.predict with a feature collection (e.g. to retrieve neighbors in cross-validation analysis), if the user requests neighbors from all features in a collection and that collection is larger than ~2000 features, GEE will likely throw User memory lmit exceeded. errors. Note that this doesn't cause a problem if the user exports the features, but if they want synchronous retrieval of the features (e.g. through .getInfo), this error appears.

One can replicate this behavior in the GEE playground using random data with 3000 plots and 8 features and using ee.Classifier.minimumDistance to retrieve neighbors for this same feature collection. When profiling this code, the user consumes ~4.2 GB of memory in the call to .classify.

https://code.earthengine.google.com/95b40c7e7e386cd41d2585affdb3dd8f

The likely solution (at least on the server side through GEE) is to call .classify repeatedly with smaller sets of features and stitch together the feature collections at the end.

@grovduck grovduck self-assigned this Mar 15, 2024
@grovduck grovduck added the bug Something isn't working label Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant