| ▲ | seabrookmx 2 hours ago | |
> So a lot of 1- CPU Kubernetes pods have been on serial all along I don't think this is true. Setting your CPU limit to 1 in Kubernetes does not mean the container sees a single logical processor. It only means the kernel allows it to use 1 core worth of CPU _time_. If your k8s node is an 8 core node, Java will still see 8 logical processors. It just means you can only use 1/8th of each, or all of one, or some combination in-between. I've never seen a k8s node running on a single core VM, as most of the cloud providers only use these for their free tier or shared core VM's for the lightest of light workloads. | ||
| ▲ | rileymichael an hour ago | parent [-] | |
> Setting your CPU limit to 1 in Kubernetes does not mean the container sees a single logical processor that's incorrect, the jvm has been container aware for nearly a decade (https://bugs.openjdk.org/browse/JDK-8146115) you are correct about the underlying scheduling. limits don't pin you to a core, you get quotas across all available | ||