-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
contractor is now slower #32
Comments
This is expected behavior because the data representation changed. |
ok. osrm being more thorough now? :-) |
Yes and no. OSRM has a certain way to handle turn restrictions. Instead of single street segments all possible turns are preprocessed. This is computationally more expensive. Am 29.11.2011 um 07:56 schrieb Emil Tin [email protected]:
|
ok i see. although it seems there are only 37 restrictions in all of copenhagen: |
this seems to be faster again? |
Yes. I don't have any specific numbers but it's faster than when we talked about it last time. Preprocessing speed is a bit of a moving target. |
this difference is huge; feels like perhaps 10x |
This is way too much for any of the changes. Did you use it in debug mode previously? Release mode is benefitting strongly from compiler optimizations. Am 17.12.2011 um 17:17 schrieb Emil Tin [email protected]:
|
as long as things get 10x faster i don't complain :-) so far i've disabled any optimization on mac; no openmp, always just thread. i still manage to contract most of copenhagen in 6 sec |
looking at sconstruct i see that it includes these lines even on mac: if GetOption('buildconfiguration') == 'debug': since i'm not using the debug switch i am in fact using optimization. but i'm not using openmp; that part is not included if the platform is mac. |
after the last round of updates, the contractor takes much longer to complete. in the 'preprocesssing' steps, the first part is very fast, but the last part takes a long time. the last 5% takes longer that the previous 95%. i don't think this was the case before.
The text was updated successfully, but these errors were encountered: