Does anyone know if CPU limits are enforced on GKE 1.3 or 1.4? On Tuesday, 15 March 2016 02:50:33 UTC+2, Vishnu Kannan wrote: > > CPU will not be throttled in GKE. CPU limits will not be enforced. Under > contention, CPU requests will be enforced though. > This will change in the near future, most likely in v1.3 release. > > On Mon, Mar 14, 2016 at 2:24 PM, Zaar Hai <hai...@gmail.com <javascript:>> > wrote: > >> I'm running on GKE cluster v1.1.8 and testing resource enforcement. >> >> I've created a simple script >> <https://gist.github.com/haizaar/91469f5c4dfdef1f1965#file-cpu_loader-py> >> that crunches numbers and measures speed. I've wrapped it into docker >> image >> <https://gist.github.com/haizaar/91469f5c4dfdef1f1965#file-dockerfile-cpu-loader> >> >> and launched through pod on my single n1-highcpu-4 node cluster. It was >> able to crunch 30k loops/sec and I saw node CPU was 100% utilized. Now I've >> added limits specification: >> >> apiVersion: v1 >> kind: Pod >> metadata: >> name: cpu-small >> spec: >> containers: >> - image: docker.io/haizaar/cpu-loader:1.1 >> name: cpu-small >> resources: >> requests: >> cpu: "100m" >> limits: >> cpu: "100m" >> >> I recreated the pod and verified that my limits are indeed applied: >> Non-terminated Pods: (6 in total) >> Namespace Name >> CPU Requests CPU Limits Memory >> Requests Memory Limits >> ───────── ──── >> ──────────── ────────── >> ─────────────── ───────────── >> default cpu-small >> 100m (2%) 100m (2%) 0 (0%) >> 0 (0%) >> kube-system >> fluentd-cloud-logging-gke-limits-test-aec280e3-node-2tdw >> 100m (2%) 100m (2%) 200Mi (5%) 200Mi (5%) >> kube-system heapster-v11-9rqvl >> 100m (2%) 100m (2%) 212Mi (5%) >> 212Mi (5%) >> kube-system kube-dns-v9-kbzpd >> 310m (7%) 310m (7%) 170Mi (4%) >> 170Mi (4%) >> kube-system kube-ui-v4-7q12m >> 100m (2%) 100m (2%) 50Mi (1%) >> 50Mi (1%) >> kube-system l7-lb-controller-v0.5.2-imjry >> 110m (2%) 110m (2%) 70Mi (1%) >> 120Mi (3%) >> >> >> However I still see that it happily crunches 30k loops/sec and instance >> CPU is 100%. From documentation >> <https://github.com/kubernetes/kubernetes/blob/release-1.2/docs/proposals/resource-qos.md#compressible-resource-guarantees> >> >> I read that *Containers will be throttled if they exceed their [CPU] >> limit*. However this does not seem to be the case. Am I missing >> something? >> >> Thanks, >> Zaar >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Containers at Google" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to google-contain...@googlegroups.com <javascript:>. >> To post to this group, send email to google-c...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/google-containers. >> For more options, visit https://groups.google.com/d/optout. >> > >
-- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
