OOM kills the process due to lack of memory #59
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
…return anything in the pytzwhere implementation now does, due to the way geodjango-tzwhere queries for the nearest timezone. This seems acceptable since it is returning a nearby timezone.
… tool seems the same, but the migration takes way less time this way.
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.
Querying the time zone by coordinates, eats more than 500MB of memory, which causes my product to stop on the server.
Are there any examples of code optimization?
.service: Main process exited, code=killed, status=9/KILL
.service: Failed with result 'signal'.
**from tzwhere import tzwhere
async def get_tz(latitude, longitude):
tz = tzwhere.tzwhere(forceTZ=True)
tz = tz.tzNameAt(latitude, longitude, forceTZ=True)
return tz**