-
-
Notifications
You must be signed in to change notification settings - Fork 222
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 issue #84
Comments
As the author of the code in question I can tell you that it's unlikely that the algorithm I used will work for the planet regardless of how much RAM you throw at it. You should consider these errors as fatal and follow the instructions in the warning message I left. |
Please don't use the issue tracker for general support, this case was clearly documented in the error message you provided along with a solution. |
I thought that valhalla was already being used by the docker install , having seen the ~/pelias/images/valhalla dir and dockerfile. |
I tried using a valhalla-generated file (the one conveniently linked to here) , putting
into ~/pelias/projects/planet/polylines/pelias.json after putting the unzipped/renamed polylines file at /tmp/pelias/planet/data/polylines/road_network.polylines (my DATA_DIR being /tmp/pelias/planet/data), ran
which was the previously-used polylines file . Is this expected ? Trying again with |
ok it looks like you DON'T run |
Suggestion: Why not roll valhalla into pelias as a dependency, and when a file is too large, pelias' prepare script could execute the valhalla scripts for you. |
FYI I just added this 3 days ago https://github.com/pelias/docker-valhalla-baseimage |
I hit an out-of-memory on a 64Gb ram aws machine during 'prepare all' for planet . The process continues so I am not sure how that impacts the geocoder, if at all :
btw
prepare all
consistently manages to somehow munge up the terminal display , preventing newlines from going to the begninning of the next line - that's happened on 2 debian jessie machines and one ubuntu 18 machine . most of the output above had a bunch of spaces everywhere, i left the first few lines as isIn any case I suppose the issue is either
The text was updated successfully, but these errors were encountered: