-
Notifications
You must be signed in to change notification settings - Fork 536
improve redis getkeyversion #3990
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
Conversation
Signed-off-by: Filinto Duran <[email protected]>
Signed-off-by: Filinto Duran <[email protected]>
Signed-off-by: Filinto Duran <[email protected]>
Signed-off-by: Filinto Duran <[email protected]>
Signed-off-by: Filinto Duran <[email protected]>
Signed-off-by: Filinto Duran <[email protected]>
Signed-off-by: Filinto Duran <[email protected]>
… not added just comparison) Signed-off-by: Filinto Duran <[email protected]>
Signed-off-by: Filinto Duran <[email protected]>
Signed-off-by: Filinto Duran <[email protected]>
Signed-off-by: Filinto Duran <[email protected]>
|
||
// ~8x speed - ~1/2 allocations | ||
|
||
// unsafe comparison |
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 is just for comparison with a run changing toString method to use unsafe []byte->string. In many cases it would be fine but leaving for future if really needed it could be added as an option
@yaron2 should I put this in the 1.16 branch? or leave for later |
Linter needs go mod tidy |
@yaron2 I think that was coming from the main branch after I updated it here, but it seems fine after you updated it again |
Signed-off-by: Filinto Duran <[email protected]> Co-authored-by: Yaron Schneider <[email protected]>
Description
After checking some profiling in one of our programs that makes use of this method, we noticed that a lot of the allocations and cpu time was sunk on this method
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:
Note: We expect contributors to open a corresponding documentation PR in the dapr/docs repository. As the implementer, you are the best person to document your work! Implementation PRs will not be merged until the documentation PR is opened and ready for review.