Enlarge droplet to 64GB RAM to avoid memory error #561
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When running the `/contrib/crontab/update` task, the `TraveledSpeedsClassifier` was raising `MemoryError` in it's `predict` method (line 70). This is a temporary solve. We should investigate if this memory consumption can be reduced.
This was referenced Aug 23, 2021
|
As these droplets (virtual machines, for those not familiar with DigitalOcean jargon) are short-lived, this might not be only a temporary fix. I think it worth it to deploy and check how much the bill raises at the end of the month. If that is a considerable amount, then we could try to find a better way… Maybe finally it is time for Dask ✨ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When running the
/contrib/crontab/updatetask, theTraveledSpeedsClassifierwas raisingMemoryErrorin it'spredictmethod (line 70).This is a temporary solve. We should investigate if this memory consumption can be reduced.
This issue is further described in #560.
Fixes:
#556