Support for counters, partial data with pieces arriving out of sync #6
Conversation
This file contains hidden or 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
+ atomic counters with the resulting counter value returned to the caller + support for partial data collection; the complete data is returned upon completion fixed: + multiple caches being initialized, one for each worker baseline ops per sec ~ 10K/sec
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.
Robby, thank you for the node-lry-cache above all!
Made some modifications to better serve what we do at Peerbelt. Thought atomic counters and binding together data pieces becoming available out of sync may be of interest to others, hence the pull request.
On the downside, refactored some code looking for better performance, even though V8 is likely performing optimization anyway.. Let me know your thought.
Cheers,
-Krassi