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

Routing table is currently a Map --- use something more performant #3

Open
rlupton20 opened this issue Jul 20, 2016 · 0 comments
Open

Comments

@rlupton20
Copy link
Owner

For small 256 address subnets, a vector would be better (O(1) lookup and delete etc.). For larger networks (less likely use case) a HashMap might be better.

The current Map data structure, is O(log n) in most operations.

Migrate the internal router to a better data structure.

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

No branches or pull requests

1 participant