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

Running osrm-extract on us-latest.osm.pbf #6448

Closed
fitzg2 opened this issue Nov 8, 2022 · 12 comments
Closed

Running osrm-extract on us-latest.osm.pbf #6448

fitzg2 opened this issue Nov 8, 2022 · 12 comments
Labels

Comments

@fitzg2
Copy link

fitzg2 commented Nov 8, 2022

Has anybody tried to run

docker run -t -v "${PWD}:/data" ghcr.io/project-osrm/osrm-backend osrm-extract -p /opt/car.lua /data/us-latest.osm.pbf

on http://download.geofabrik.de/north-america/us-latest.osm.pbf ?

It's not generating the OSRM files to run osrm-partition and customize

@fitzg2 fitzg2 added the question label Nov 8, 2022
@SiarheiFedartsou
Copy link
Member

What do you have as an output of this command? Are you sure you have enough RAM?

@fitzg2
Copy link
Author

fitzg2 commented Nov 8, 2022

It seems to be exiting correctly. It doesn't output any error. Tried with a GCP e2-standard-16 instance. So 64gb ram 16 cores.

@SiarheiFedartsou
Copy link
Member

It seems to be exiting correctly. It doesn't output any error. Tried with a GCP e2-standard-16 instance. So 64gb ram 16 cores.

Could provide output of command?

@fitzg2
Copy link
Author

fitzg2 commented Nov 9, 2022

@SiarheiFedartsou here's the entire output

https://hastebin.com/raw/ajivivisap

@SiarheiFedartsou
Copy link
Member

@SiarheiFedartsou here's the entire output

https://hastebin.com/raw/ajivivisap

Succesfull osrm-extract run is usually finished with smth like:

[2022-11-09T16:57:38.626991] [info] RAM: peak bytes used: 596377600

What is not a case here. Can you try smaller .osm.pbf? E.g. berlin-latest.osm.pbf from README?

@williamknn
Copy link

williamknn commented Nov 10, 2022

I'm with the same problem, it seems apparently exited with success but the osrm file is not generated. See the output here: https://gist.github.com/williamknn/6e4418b83841ff9b1717b9b09df5f569

I've tried with a smaller map (mexico) but the result is the same.

AWS m5.8xlarge (128.0 GiB | 32 vCPUs)
Ubuntu 20.04
libboost1.73
lua5.3

@SiarheiFedartsou
Copy link
Member

but the osrm file is not generated

Do you expect file with .osrm extension to be generated? We recently got rid of it #6354, it is was intermediate artefact of osrm-extract which is not actually not needed in other parts of OSRM.

@williamknn
Copy link

williamknn commented Nov 10, 2022

but the osrm file is not generated

Do you expect file with .osrm extension to be generated? We recently got rid of it #6354, it is was intermediate artefact of osrm-extract which is not actually not needed in other parts of OSRM.

So how do I build the map now? How can I run the contract? Sorry but after this release I don't find anything about this in wiki pages.

PS: Even using --dump-nbg-graph as an argument the file still not being generated.

@williamknn
Copy link

williamknn commented Nov 10, 2022

I think now I understood how this works... I thought that contract uses the .osrm file as input and then changes it but it doesn't. The .osrm file generated by the extract is only for debug pourposes and contract uses the entire directory to generate the file. Am I correct?

I think this needs to be clear in documentation to avoid this kind of misunderstanding.

@SiarheiFedartsou
Copy link
Member

@williamknn exactly. I would be happy to approve and merge any PRs improving our documentation :)

@fitzg2
Copy link
Author

fitzg2 commented Nov 16, 2022

@SiarheiFedartsou how much memory would it take to process https://download.geofabrik.de/north-america/us-latest.osm.pbf ?
would it be better to process special sub regions and serve them under different ports?

@fitzg2
Copy link
Author

fitzg2 commented Nov 17, 2022

Got it to process us-latest.osm.pbf on a 256gb ram + 32vcpu droplet for anyone interested. Didn't measure the time.

@fitzg2 fitzg2 closed this as completed Nov 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants