Optimize dynamic IP allocation algorithm by storing the last dynamically allocated IP #179
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ount To optimize dynamic allocations we will save the IP we last allocated from the pool. During the next dynamic allocation we will start looking from this index to save time, rather than always looping over from the beginning.
When an IP is dynamically allocated we save it into Pool/Pool6. Next time searching for the first free IP will start from the associated index, rather than from zero. This should accelerate allocation time for huge allocation pools (4/8M).
Levovar
force-pushed
the
ipam_store_last_ip
branch
from
6cf4163 to
5e7980d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When an IP is dynamically allocated we save it into Pool/Pool6. Next time searching for the first free IP will start from the associated index, rather than from zero.
This should accelerate allocation time for huge allocation pools (4/8M).
Works with both V4/V6 subnets!