Hi, I’m not sure if this is the right place for this question. In case it isn’t, I would appreciate if someone can direct me to the right one.
I have one node with one service that sends only one request to elastic cache. The node have one core only physically.
When I change the number of requested CPU’s in the pod, let’s say from 1 to 3 (does not make sense, does it?), and the service sends this one request to elastic cache, the latency of the request gets better.
In this case I’m using elastic cache, but I really do not think it matters.
Any idea what I observe the change of the latency? Isn’t k8s ignore the number of requested CPU’s in case it is greater than the actual number?
Thanks!!
You can’t request more cores than are available on a node. That should not get scheduled. If you think that it is being scheduled, I would love to see a concrete reproduction case.
That doesn’t really answer your question about latency, but I don’t know how to answer that with this misunderstanding hanging.