Preallocate deque used for the filter window #107
Merged
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
This is needed on some platforms to ensure that the needed space is already allocated before adding values (e.g. Windows). That said, this should be a bit faster than adding values to the filter window at the time and potentially going through several reallocations in the process. By using this approach, we guarantee that only one allocation occurs when creating and initially filling the deque. Ideally there should be no reallocations in the filter code as we keep this size as an upper bound (though we do go under by 1 periodically).
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.
This is needed on some platforms to ensure that the needed space is already allocated before adding values (e.g. Windows). That said, this should be a bit faster than adding values to the filter window at the time and potentially going through several reallocations in the process. By using this approach, we guarantee that only one allocation occurs when creating and initially filling the deque. Ideally there should be no reallocations in the filter code as we keep this size as an upper bound (though we do go under by 1 periodically).