Replies: 2 comments 5 replies
-
It seems there are only two issues mentioning potential performance improvements: #92 and #93. I'm not sure it's possible to implement the changes proposed in #92 because |
Beta Was this translation helpful? Give feedback.
5 replies
-
An additional change could be an atomic per item CAS (compare and swap)
data structure as backing store. Better than sharding, which is an O(1)
solution.
Op ma 5 jun. 2023 08:06 schreef Gökhan Özeloğlu ***@***.***>:
… Yes, you are right. Get depends on ttl update. Maybe the
MGetWithoutTouchingOnHit method can be implemented. It will be worked
when disableTouchOnHit = true. If it is false, the
MGetWithoutTouchingOnHit returns nil or error.
—
Reply to this email directly, view it on GitHub
<#105 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAW5D6ARGCDDUOW3CQ3UDATXJVZPTANCNFSM6AAAAAAYLOGWJI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I see that we have several issues related to performance. I would like to help with this, like to increase performance :) who can help me to go through the current solution?
Beta Was this translation helpful? Give feedback.
All reactions