-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Improve connection speed by running fewer commands #2850
Comments
Hey @chayim, |
@prabhjotsingh18 want to give it a go and ping here @ofekshenawa can possibly assist. |
Sure @chayim, @ofekshenawa if you can guide me where to begin and what concepts I need to familiarise myself with. |
@prabhjotsingh18 are you still working on this? |
hey @pglushko , |
@pglushko are you actively working on this task? If not, please let me know. I would love to work on this issue. I would like to know how connections are working in Redis. |
@chayim and @ofekshenawa, I am not sure if anyone is working on this issue or not. If not, I would like to work on it to learn. I would like your guidance on where to start. |
It seems like this has already been the case since #326 or am I missing something? https://github.com/redis/go-redis/pull/326/files#diff-190fc9ceda3bbdbe723d493b8b99e2b9a0100c7d635bfe9b04246280bef6f67e |
Today, connecting to a Redis instance, involves running multiple commands, and parsing the response repeatedly, this includes usage such as setinfo, which itself is run twice. The example below illustrates, that it's possible to pass all connection configuration information within a pipeline. In turn, the HELLO call returns the version of Redis, which could perhaps be used later for other things.
This is marked as good-first-issue not because it's necessarily easy to implement, inasmuch as it's a good entrypoint, to learning how connections to redis occur.
The text was updated successfully, but these errors were encountered: