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

Planet build too slow, docker multiprocessing/parallel processing for interpolation #134

Closed
imran-5 opened this issue Sep 14, 2019 · 5 comments

Comments

@imran-5
Copy link

imran-5 commented Sep 14, 2019

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 and pelias prepare all, not using threads/core or parallel scripting,
during planet build, 2-3 scripts use the parallel processing.

image
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 and Pelias prepare all?

@imran-5 imran-5 changed the title Docker multiprocessing Issue planet build too slow Planet build too slow, docker multiprocessing Sep 14, 2019
@imran-5 imran-5 changed the title Planet build too slow, docker multiprocessing Planet build too slow, docker multiprocessing, parallel processing for interpolation Sep 15, 2019
@imran-5 imran-5 changed the title Planet build too slow, docker multiprocessing, parallel processing for interpolation Planet build too slow, docker multiprocessing/parallel processing for interpolation Sep 15, 2019
@missinglink
Copy link
Member

Hi @I1mran, the prepare steps aren't included in the time estimate.

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.

@imran-5
Copy link
Author

imran-5 commented Sep 16, 2019

Thanks for the reply,

I am watching this potential update for interpolation.
pelias/interpolation#212
I will be in touch with geocode.earth for the planet build database soon.

Thanks.

@imran-5 imran-5 closed this as completed Sep 16, 2019
@imran-5 imran-5 reopened this Sep 16, 2019
@orangejulius
Copy link
Member

Hi folks,
Just doing some issue cleanup :)

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.

@answerquest
Copy link

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?

@meezaan
Copy link

meezaan commented Feb 29, 2024

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 and pelias prepare all, not using threads/core or parallel scripting, during planet build, 2-3 scripts use the parallel processing.

image 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 and Pelias prepare all?

What kind of cores are you using? If I run it on baremetal with 12 physical cores (24 threads of vCPUs, if you will) the entire planet build takes about 24 hours.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants