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

The dijkstra's implementation should be bidirectional #7

Closed
PayasR opened this issue Aug 11, 2019 · 2 comments
Closed

The dijkstra's implementation should be bidirectional #7

PayasR opened this issue Aug 11, 2019 · 2 comments

Comments

@PayasR
Copy link

PayasR commented Aug 11, 2019

There are still some perf gains to be had if we switch to a bidirectional dijkstra's implementation for the query phase.
(See https://arxiv.org/pdf/1504.05140.pdf , pages 22-23)

@easbar
Copy link
Owner

easbar commented Aug 11, 2019

The query algorithm already is bidirectional, see here. IMO the easiest way to improve query speed at the moment would be to implement stall on demand, something like this.

@PayasR
Copy link
Author

PayasR commented Aug 11, 2019

Oh okay, I was looking at this instead. Yes, stalling is needed too.. do you have it on the To-Do list? I don't see any project roadmap available on GitHub..

@PayasR PayasR closed this as completed Apr 1, 2020
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

2 participants