Re: [OSRM-talk] Expecting time for osrm-contract for planet

an SSD drive make? > -- > *From:* Daniel Patterson <dan...@mapbox.com> > *Sent:* Friday, September 22, 2017 8:05:56 AM > *To:* Mailing list to discuss Project OSRM > *Subject:* Re: [OSRM-talk] Expecting time for osrm-contract for planet > > Hi Kieran, > > We don't, but

Re: [OSRM-talk] Expecting time for osrm-contract for planet

? From: Daniel Patterson <dan...@mapbox.com> Sent: Friday, September 22, 2017 8:05:56 AM To: Mailing list to discuss Project OSRM Subject: Re: [OSRM-talk] Expecting time for osrm-contract for planet Hi Kieran, We don't, but I've done some profiling in the past,

Re: [OSRM-talk] Expecting time for osrm-contract for planet

Hi Kieran, We don't, but I've done some profiling in the past, Docker itself should have negligible impact. The two things that might be slowing things down: 1) The docker images don't bundle jemalloc (http://jemalloc.net/), which can speed things up by 10-15% 2) osrm-contract is

Re: [OSRM-talk] Expecting time for osrm-contract for planet

Hi Daniel, Can you clarify if you use Docker at Mapbox? What kind of server do you guys have (if not the one described on the wiki page)? Over night, the process has gone to just 75% complete from 65% yesterday - 41 hours in total now, and back to maxing CPU again. Kind regards, Kieran

Re: [OSRM-talk] Expecting time for osrm-contract for planet

OSRM supports *two* core routing algorithms - CH and MLD. The `osrm-contract` tool generates the CH dataset, but you can use the MLD pipeline instead with: osrm-extract -p profiles/bicycle.lua yourmap.osm.pbf osrm-partition yourmap.osrm osrm-customize yourmap.osrm osrm-routed -a MLD yourmap.osrm

Re: [OSRM-talk] Expecting time for osrm-contract for planet

I take back what I said, the contract process has advanced 5%! Looks like it's now using more RAM than CPU, so I'll give it a bit more time before judging it prematurely again :-) Kind regards, Kieran Caplice On 21/09/17 17:03, Kieran Caplice wrote: We're actually looking for the best of

Re: [OSRM-talk] Expecting time for osrm-contract for planet

i've run into the same issues, and now i just use metroextracts of the areas that i need for the bike stuff i do and it reduces the time significantly *Alex Farioletti* *415.312.1674* *tcbcourier.com * On Thu, Sep 21, 2017 at 8:49 AM, Kieran Caplice

Re: [OSRM-talk] Expecting time for osrm-contract for planet

Thanks Daniel. I'm using the bicycle profile, so I would expect based on what you've said that somewhere up to 36 hours would be likely. However, this is the current output, after 25h40m: [info] Input file: /data/1505492056/planet-latest.osrm [info] Threads: 12 [info] Reading node weights.

Re: [OSRM-talk] Expecting time for osrm-contract for planet

Hi Kieran, The contraction time will be slow - many, many hours for the whole planet. *Typically* for the car profile it's about 12 hours, but if you use bike or foot, or your own profile, it can get a lot bigger. If you've messed with the travel speeds, that can have a big effect too. 24

[OSRM-talk] Expecting time for osrm-contract for planet

Hi all, Could anyone give an approx estimate for the time required to run the osrm-contract on planet data on a 12 thread, 256 GB RAM, SSD machine? The osrm-extract process finished in 232 minutes, but the contract has now been running solid for 24 hours, and appears to be stuck at 60% on