-
Notifications
You must be signed in to change notification settings - Fork 20
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
Improving perf when using InMemory storage #186
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
alexsnaps
reviewed
Jun 16, 2023
didierofrivia
force-pushed
the
faster-baby-ii
branch
from
June 26, 2023 13:58
44310d0
to
ae0084c
Compare
didierofrivia
force-pushed
the
faster-baby-ii
branch
from
July 3, 2023 15:02
6ec5b78
to
3c1ed26
Compare
didierofrivia
changed the title
Faster baby ii
Improving perf when getting limits InMemory storage
Jul 3, 2023
didierofrivia
changed the title
Improving perf when getting limits InMemory storage
Improving perf when using InMemory storage
Jul 4, 2023
alexsnaps
requested changes
Jul 8, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks real good to me, if we could at least clean up the repetition there…
didierofrivia
force-pushed
the
faster-baby-ii
branch
from
July 10, 2023 14:11
3c1ed26
to
2fafbed
Compare
* Storing now in ExpiringValue type within the main structure of nested HashMaps
* Making first loop faster not modifying counters, read only * Second loop updates de counters [refactor] Refactoring inMemory, check when load_counters in Vacant branch [refactor] Refactoring inMemory -> fixing performance in check _and_update [refactor] Refactoring InMemory -> first loop faster, not modifying storage
didierofrivia
force-pushed
the
faster-baby-ii
branch
from
July 10, 2023 14:12
2fafbed
to
326986b
Compare
alexsnaps
approved these changes
Jul 10, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙌
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 also part of #183
Criterion performance results for In Memory storage, check_rate_limited_and_update function
10 namespaces with 10 limits each with 10 conditions and 10 variables
10 namespaces with 50 limits each with 10 conditions and 10 variables