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

[performance] Refactor RouteProcessor's edge time generation #122

Open
kuanb opened this issue Dec 24, 2018 · 0 comments
Open

[performance] Refactor RouteProcessor's edge time generation #122

kuanb opened this issue Dec 24, 2018 · 0 comments

Comments

@kuanb
Copy link
Owner

kuanb commented Dec 24, 2018

Edge time generation is where most of runtime is spent. The below image demonstrates the breakdown of time by each route in the AC Transit GTFS feed:

eval-time-cost-route-processor

Total runtime is ~10-11 seconds on my current machine. Using mp increases that to 11-12 seconds (this is bad). Inefficiencies are tied up in the execution of the generate_all_observed_edge_costs method within generate_route_costs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant