-
-
Notifications
You must be signed in to change notification settings - Fork 669
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
improve: review of everything using set #1705
Merged
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
luan
approved these changes
Oct 24, 2023
dudantas
approved these changes
Oct 26, 2023
Kudos, SonarCloud Quality Gate passed! |
marcusvcj
pushed a commit
to marcusvcj/canary
that referenced
this pull request
Nov 4, 2023
Refactor set implementation across the codebase for optimal performance. Detailed Description: This encompasses a comprehensive review and overhaul of `std::set` usage within the project, replacing it with more efficient collections as applicable. The refactoring targets instances where set operations are utilized, with a critical analysis of performance considerations. Key Changes: • Avoid `std::set` due to ordering overhead when order is not a requirement. • Employ `std::unordered_set` for scenarios with infrequent insertions and deletions but frequent searches. • Integrate `phmap::flat_hash_set` as a balanced option for various operations without linear searches. • Introduce `vector_set` for batch insertions and short-term unique data handling within methods. Performance Insights: The `vector_set` is particularly notable for its batch insertion efficiency and automatic sorting and deduplication upon search or deletion operations, making it suitable for maintaining a unique set of elements temporarily. Example Usage: stdext::vector_set<int> unique_list; unique_list.insertAll({1, 3, 4, 5}); unique_list.insertAll({4, 2, 87, 2}); unique_list.insertAll({3, 1, 99, 5}); unique_list now contains 1, 2, 3, 4, 5, 87, 99 without duplicates
marcusvcj
pushed a commit
to marcusvcj/canary
that referenced
this pull request
Nov 20, 2023
Refactor set implementation across the codebase for optimal performance. Detailed Description: This encompasses a comprehensive review and overhaul of `std::set` usage within the project, replacing it with more efficient collections as applicable. The refactoring targets instances where set operations are utilized, with a critical analysis of performance considerations. Key Changes: • Avoid `std::set` due to ordering overhead when order is not a requirement. • Employ `std::unordered_set` for scenarios with infrequent insertions and deletions but frequent searches. • Integrate `phmap::flat_hash_set` as a balanced option for various operations without linear searches. • Introduce `vector_set` for batch insertions and short-term unique data handling within methods. Performance Insights: The `vector_set` is particularly notable for its batch insertion efficiency and automatic sorting and deduplication upon search or deletion operations, making it suitable for maintaining a unique set of elements temporarily. Example Usage: stdext::vector_set<int> unique_list; unique_list.insertAll({1, 3, 4, 5}); unique_list.insertAll({4, 2, 87, 2}); unique_list.insertAll({3, 1, 99, 5}); unique_list now contains 1, 2, 3, 4, 5, 87, 99 without duplicates
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 PR aims to exchange for the best set or for another more viable collection.
when to use???
Benchmark
