geirke
there seems to be a significant slowdown in calculation if start and target are the same location
The slowdown comes after a certain number of requests to Google Maps API per day (then you get throttled), and is not associated with A-Z vs. roundtrip mode. The time spent in route computation is almost solely waiting for Google Maps directions requests, and not the solve part (usually takes less than a second at the very end after all pairs of directions are looked up).
Geir
2016-08-20 2:34 GMT+02:00 elypter [email protected]:
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/geirke/optimap/issues/4, or mute the thread https://github.com/notifications/unsubscribe-auth/ABGRA2WFQpntX6KXYDv-I-l8R4OURsKZks5qhkuEgaJpZM4Jo9A9 .
ah, thanks, that explains the inconsistent waiting times. maybe the new routing algorithm in osm could be an alternative