4 ms·
Wouldn't Kubernetes and/or Dapr just add even more latency before the packets reach Redis? It seems like the parent comment's author is implying that Redis is
by joshribakoff 4y ago
Wouldn't Kubernetes and/or Dapr just add even more latency before the packets reach Redis?
It seems like the parent comment's author is implying that Redis is already too slow even when running it on bare metal and connecting directly to it.
Adding additional things like service discovery and proxies in the network path will not speed it up. To speed it up you would need to bring Redis closer, so perhaps you meant using k8 tools like "pod topology spread contraints" to do so (juxtaposing with the default k8 behavior that may spread workloads out in an undesirable manner)?
Simply going from "we are not using k8s" to "we are using k8s" won't speed up latency to Redis.
- llamaLord 4y agoI was under the assumption OP's redis instance was running on a separate machine and they wanted to be and to achieve a setup that "felt like" it was distributed (container isolation, etc) but without the network hops adding in latency. My question was more around whether you could use K8's to effectively simulate that, but on a single beefy machine to remove the network hops. It was also a curiosity "is this possible" type of question, not an "I'm saying this is a good idea" type of question.