You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current TravelTimeCalculator seems overly complicated with multiple variants and levels of inheritance and delegation to store the travel times (on-link or link-to-link).
While developing and performance-tuning SpeedyALT, I made the observation that the travel time lookup adds a larger than expected overhead to the routing.
Looking at the current functionality of TravelTimeCalculator, I think the storage backend (at least for on-link travel times) could be implemented in a more resource-efficient and performance-optimized way, resulting in cleaner code, higher efficiency and better performance.
The current TravelTimeCalculator seems overly complicated with multiple variants and levels of inheritance and delegation to store the travel times (on-link or link-to-link).
While developing and performance-tuning SpeedyALT, I made the observation that the travel time lookup adds a larger than expected overhead to the routing.
Looking at the current functionality of TravelTimeCalculator, I think the storage backend (at least for on-link travel times) could be implemented in a more resource-efficient and performance-optimized way, resulting in cleaner code, higher efficiency and better performance.
Maybe related: #1933, #1935
The text was updated successfully, but these errors were encountered: