Replies: 1 comment 1 reply
-
@vmihailenco What's your opinion? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Support for redis.RESP3, it is difficult to maintain the current performance of RESP2. According to my test, it will cause a 5-10% performance drop, which is about an increase of 100-400ns/op(The way to use #1716).
This is because the RESP3 protocol adds an Attribute type, which looks like this:
The current command->proto.Reader cannot handle it, and a processing method similar to #1716 (proto.Value) needs to be used, unless we abandon this type.
Beta Was this translation helpful? Give feedback.
All reactions