-
-
Notifications
You must be signed in to change notification settings - Fork 233
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
Planet build too slow, docker multiprocessing/parallel processing for interpolation #134
Comments
Hi @I1mran, the The interpolation build is single-threaded and can take a very long time to build for the whole world, you should save a copy and avoid rebuilding those databases often. |
Thanks for the reply, I am watching this potential update for interpolation. Thanks. |
Hi folks, The interpolation builds do indeed take a long time, and are single threaded. We generally recommend skipping the interpolation build when initially experiment with Pelias to save time. It can run for 6+ days. |
So what exactly do we lose when we skip the interpolation step in the whole pelias process? Do all the POIs from OSM and all the addresses from openaddresses still make it to the output? |
Hey team!
I am using docker Pelias for planet build,
the server is 192gb ram, 48 cores, SSD 1tb.
The docker build is too slow for
pelias interpolation prepare
andpelias prepare all
, not using threads/core or parallel scripting,during planet build, 2-3 scripts use the parallel processing.
it's over 2 days and the interpolation part is not finished.
according to your documentation, it will take around 16 hours with 32 cores server to build a planet.
Is there any way to use parallel scripting for
planet interpolation prepare
andPelias prepare all
?The text was updated successfully, but these errors were encountered: