Optimizing Kubernetes Resource Requests/Limits for Cost-Efficiency and Latency - JAX DevOps London

JAX DEVOPS
LONDON
2019-05-15
HENNING JACOBS
@try_except_
Optimizing
Kubernetes
Resource
Requests/Limits

2
EUROPE’S LEADING ONLINE FASHION PLATFORM

3
ZALANDO AT A GLANCE
~ 5.4billion EUR
revenue 2018
> 250
million
visits
per
month
> 15.000
employees in
Europe
> 79%
of visits via
mobile devices
> 26
million
active customers
> 300.000
product choices
~ 2.000
brands
17
countries

4
SCALE
118Clusters
380Accounts

7
Is this a lot? Is this cost efficient?

8
¯_(ツ)_/¯
Do you know your per unit costs?

9
THE MAGIC DIAL
Speed
Stability
Overprovision
Higher Cost
Efficiency
Risk
Overcommit
Lower Cost

11
KUBERNETES: IT'S ALL ABOUT RESOURCES
Node Node
Pods demand capacity
Nodes offer capacity
Scheduler

12
COMPUTE RESOURCE TYPES
● CPU
● Memory
● Local ephemeral storage (1.12+)
● Extended Resources
○ GPU
○ TPU?
Node

13
KUBERNETES RESOURCES
CPU
○ Base: 1 AWS vCPU (or GCP Core or ..)
○ Example: 100m (0.1 vCPU, "100 Millicores")
Memory
○ Base: 1 Byte
○ Example: 500Mi (500 MiB memory)

14
REQUESTS / LIMITS
Requests
○ Affect Scheduling Decision
○ Priority (CPU, OOM adjust)
Limits
○ Limit maximum container usage
resources:
requests:
cpu: 100m
memory: 300Mi
limits:
cpu: 1
memory: 300Mi

15
Pod 1
REQUESTS: POD SCHEDULING
CPU
Memory
Pod 2CPU
Memory
Node 1
Node 2
CPU
Memory
Pod 3
Requests

16
POD SCHEDULING
CPU
Memory
CPU
Memory
Node 1
Node 2
Pod 4

17
POD SCHEDULING: TRY TO FIT
CPU
Memory
CPU
Memory
Node 1
Node 2

18
POD SCHEDULING: NO CAPACITY
CPU
Memory
CPU
Memory
Node 1
Node 2
Pod 4
"PENDING"

19
REQUESTS: CPU SHARES
kubectl run --requests=cpu=10m/5m ..sha512()..
cat /sys/fs/cgroup/cpu/kubepods/burstable/pod5d5..0d/cpu.shares
10 // relative share of CPU time
cat /sys/fs/cgroup/cpu/kubepods/burstable/pod6e0..0d/cpu.shares
5 // relative share of CPU time
cat /sys/fs/cgroup/cpuacct/kubepods/burstable/pod5d5..0d/cpuacct.usage
/sys/fs/cgroup/cpuacct/kubepods/burstable/pod6e0..0d/cpuacct.usage
13432815283 // total CPU time in nanoseconds
7528759332 // total CPU time in nanoseconds

20
LIMITS: COMPRESSIBLE RESOURCES
Can be taken away quickly,
"only" cause slowness
CPU Throttling
200m CPU limit
⇒ container can use 0.2s of CPU time per second

21
CPU THROTTLING
docker run --cpus CPUS -it python
python -m timeit -s 'import hashlib' -n 10000 -v
'hashlib.sha512().update(b"foo")'
CPUS=1.0 3.8 - 4ms
CPUS=0.5 3.8 - 52ms
CPUS=0.2 6.8 - 88ms
CPUS=0.1 5.7 - 190ms
more CPU throttling,
slower hash computation

22
LIMITS: NON-COMPRESSIBLE RESOURCES
Hold state,
are slower to take away.
⇒ Killing (OOMKill)

23
MEMORY LIMITS: OUT OF MEMORY
kubectl get pod
NAME READY STATUS RESTARTS AGE
kube-ops-view-7bc-tcwkt 0/1 CrashLoopBackOff 3 2m
kubectl describe pod kube-ops-view-7bc-tcwkt
...
Last State: Terminated
Reason: OOMKilled
Exit Code: 137

24
QUALITY OF SERVICE (QOS)
Guaranteed: all containers have limits == requests
Burstable: some containers have limits > requests
BestEffort: no requests/limits set
kubectl describe pod …
Limits:
memory: 100Mi
Requests:
cpu: 100m
memory: 100Mi
QoS Class: Burstable

25
OVERCOMMIT
Limits > Requests ⇒ Burstable QoS ⇒ Overcommit
For CPU: fine, running into completely fair scheduling
For memory: fine, as long as demand < node capacity
https://code.fb.com/production-engineering/oomd/
Might run into unpredictable OOM
situations when demand reaches node's
memory capacity (Kernel OOM Killer)

26
LIMITS: CGROUPS
docker run --cpus 1 -m 200m --rm -it busybox
cat /sys/fs/cgroup/cpu/docker/8ab25..1c/cpu.{shares,cfs_*}
1024 // cpu.shares (default value)
100000 // cpu.cfs_period_us (100ms period length)
100000 // cpu.cfs_quota_us (total CPU time in µs consumable per period)
cat /sys/fs/cgroup/memory/docker/8ab25..1c/memory.limit_in_bytes
209715200

27
LIMITS: PROBLEMS
1. CPU CFS Quota: Latency
2. Memory: accounting, OOM behavior

28
PROBLEMS: LATENCY
https://github.com/zalando-incubator/kubernetes-on-aws/pull/923

30
PROBLEMS: HARDCODED PERIOD
https://github.com/kubernetes/kubernetes/issues/51135

31
NOW IN KUBERNETES 1.12
https://github.com/kubernetes/kubernetes/pull/63437

32
OVERLY AGGRESSIVE CFS
Usage < Limit,
but heavy
throttling

33
OVERLY AGGRESSIVE CFS: EXPERIMENT #1
CPU Period: 100ms
CPU Quota: None
Burn 5ms and sleep 100ms
⇒ Quota disabled
⇒ No Throttling expected!
https://gist.github.com/bobrik/2030ff040fad360327a5fab7a09c4ff1

34
EXPERIMENT #1: NO QUOTA, NO THROTTLING
2018/11/03 13:04:02 [0] burn took 5ms, real time so far: 5ms, cpu time so far: 6ms

35
CPU Period: 100ms
CPU Quota: 20ms
⇒ No 100ms intervals where possibly 20ms is burned
⇒ No Throttling expected!

36
EXPERIMENT #2: OVERLY AGGRESSIVE CFS

37
CPU Period: 10ms
CPU Quota: 2ms
⇒ Same 20% CPU (200m) limit, but smaller period
⇒ Throttling expected!

38
SMALLER CPU PERIOD ⇒ BETTER LATENCY

39
INCIDENT INVOLVING CPU THROTTLING
https://k8s.af

40
LIMITS: VISIBILITY
docker run --cpus 1 -m 200m --rm -it busybox top
Mem: 7369128K used, 726072K free, 128164K shrd, 303924K buff, 1208132K cached
CPU0: 14.8% usr 8.4% sys 0.2% nic 67.6% idle 8.2% io 0.0% irq 0.6% sirq

41
• Container-aware memory configuration
• JVM MaxHeap
• Container-aware processor configuration
• Thread pools
• GOMAXPROCS
• node.js cluster module
LIMITS: VISIBILITY

43
ZALANDO: DECISION
1. Forbid Memory Overcommit
• Implement mutating admission webhook
• Set requests = limits
2. Disable CPU CFS Quota in all clusters
• --cpu-cfs-quota=false

44
INGRESS LATENCY IMPROVEMENT

45
CLUSTER AUTOSCALER
Simulates the Kubernetes scheduler internally to find out..
• ..if any of the pods wouldn’t fit on existing nodes
⇒ upscale is needed
• ..if it’s possible to fit some of the pods on existing nodes
⇒ downscale is needed
⇒ Cluster size is determined by resource requests
(+ constraints)
github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler

46
AUTOSCALING BUFFER
• Cluster Autoscaler only triggers on Pending Pods
• Node provisioning is slow
⇒ Reserve extra capacity via low priority Pods
"Autoscaling Buffer Pods"

47
AUTOSCALING BUFFER
kubectl describe pod autoscaling-buffer-..zjq5 -n kube-system
...
Namespace: kube-system
Priority: -1000000
PriorityClassName: autoscaling-buffer
Containers:
pause:
Image: teapot/pause-amd64:3.1
Requests:
cpu: 1600m
memory: 6871947673
Evict if higher
priority (default)
Pod needs
capacity

48
ALLOCATABLE
Reserve resources for
system components,
Kubelet, and container runtime:
--system-reserved=
cpu=100m,memory=164Mi
--kube-reserved=
cpu=100m,memory=282Mi

49
CPU/memory requests "block" resources on nodes.
Difference between actual usage and requests → Slack
SLACK
CPU
Memory
Node
"Slack"

50
STRANDED RESOURCES
Stranded
CPU
Memory
CPU
Memory
Node 1
Node 2
Some available capacity
can become unusable /
stranded.
⇒ Reschedule, bin packing

52
KUBERNETES RESOURCE REPORT
github.com/hjacobs/kube-resource-report

53
RESOURCE REPORT: TEAMS
Sorting teams by
Slack Costs

54
RESOURCE REPORT: APPLICATIONS
"Slack"

55
RESOURCE REPORT: APPLICATIONS

56
RESOURCE REPORT: CLUSTERS
"Slack"

57
RESOURCE REPORT METRICS

58
KUBERNETES APPLICATION DASHBOARD

https://github.com/hjacobs/kube-ops-view

https://github.com/hjacobs/kube-ops-view
requested
vs used

62
VERTICAL POD AUTOSCALER (VPA)
"Some 2/3 of the (Google) Borg
users use autopilot."
- Tim Hockin
VPA: Set resource requests
automatically based on usage.

63
VPA FOR PROMETHEUS
apiVersion: autoscaling.k8s.io/v1beta2
kind: VerticalPodAutoscaler
metadata: ...
spec:
targetRef:
apiVersion: apps/v1
kind: StatefulSet
name: prometheus
updatePolicy: { updateMode: Auto }
resourcePolicy:
containerPolicies: { containerName: prometheus }
minAllowed:
memory: 512Mi
maxAllowed:
memory: 10Gi
CPU/memory

64
VERTICAL POD AUTOSCALER
limit/requests adapted by VPA

66
HORIZONTAL POD AUTOSCALER
apiVersion: autoscaling/v2beta1
kind: HorizontalPodAutoscaler
metadata:
name: myapp
spec:
scaleTargetRef:
apiVersion: apps/v1
kind: Deployment
name: myapp
minReplicas: 3
maxReplicas: 5
metrics:
- type: Resource
resource:
name: cpu
targetAverageUtilization: 100
target: ~100% of
CPU requests
...

67
HORIZONTAL POD AUTOSCALING (CUSTOM METRICS)
Queue Length
Prometheus Query
Ingress Req/s
ZMON Check
github.com/zalando-incubator/kube-metrics-adapter

68
DOWNSCALING DURING OFF-HOURS
github.com/hjacobs/kube-downscaler
Weekend

69
DOWNSCALING DURING OFF-HOURS
DEFAULT_UPTIME="Mon-Fri 07:30-20:30 CET"
annotations:
downscaler/exclude: "true"

70
ACCUMULATED WASTE
● Prototypes
● Personal test environments
● Trial runs
● Decommissioned services
● Learning/training deployments
Sounds familiar?

Example: Getting started
with Zalenium & UI Tests
Example: Step by step guide to the first UI test with Zalenium running in the
Continuous Delivery Platform. I was always afraid of UI tests because it looked too
difficult to get started, Zalenium solved this problem for me.

72
HOUSEKEEPING
● Delete prototypes
after X days
● Clean up temporary
deployments
● Remove resources
without owner

73
KUBERNETES JANITOR
● TTL and expiry date annotations, e.g.
○ set time-to-live for your test deployment
● Custom rules, e.g.
○ delete everything without "app" label after 7 days
github.com/hjacobs/kube-janitor

74
JANITOR TTL ANNOTATION
# let's try out nginx, but only for 1 hour
kubectl run nginx --image=nginx
kubectl annotate deploy nginx janitor/ttl=1h

75
CUSTOM JANITOR RULES
# require "app" label for new pods starting April 2019
- id: require-app-label-april-2019
resources:
- deployments
- statefulsets
jmespath: "!(spec.template.metadata.labels.app) &&
metadata.creationTimestamp > '2019-04-01'"
ttl: 7d

77
SPOT ASG / LAUNCH TEMPLATE
Not upstream in cluster-autoscaler (yet)

78
CLUSTER OVERHEAD: CONTROL PLANE
● GKE cluster: free
● EKS cluster: $146/month
● Zalando prod cluster: $635/month
(etcd nodes + master nodes + ELB)
Potential: fewer etcd nodes, no HA, shared control plane.

79
WHAT WORKED FOR US
● Disable CPU CFS Quota in all clusters
● Prevent memory overcommit
● Kubernetes Resource Report
● Downscaling during off-hours
● EC2 Spot

80
STABILITY ↔ EFFICIENCY
Slack
Autoscaling
Buffer
Disable
Overcommit
Cluster
Overhead
Resource
Report
HPA
VPA
Downscaler
Janitor
EC2 Spot

81
OPEN SOURCE
Kubernetes on AWS
github.com/zalando-incubator/kubernetes-on-aws
AWS ALB Ingress controller
github.com/zalando-incubator/kube-ingress-aws-controller
External DNS
github.com/kubernetes-incubator/external-dns
Postgres Operator
github.com/zalando/postgres-operator
Kubernetes Resource Report
Kubernetes Downscaler
Kubernetes Janitor

82
OTHER TALKS/POSTS
• Everything You Ever Wanted to Know About Resource Scheduling
• Inside Kubernetes Resource Management (QoS) - KubeCon 2018
• Setting Resource Requests and Limits in Kubernetes (Best Practices)
• Effectively Managing Kubernetes Resources with Cost Monitoring

QUESTIONS?
HENNING JACOBS
HEAD OF
DEVELOPER PRODUCTIVITY
henning@zalando.de
@try_except_
Illustrations by @01k

Optimizing Kubernetes Resource Requests/Limits for Cost-Efficiency and Latency - JAX DevOps London

More Related Content

What's hot (20)

Similar to Optimizing Kubernetes Resource Requests/Limits for Cost-Efficiency and Latency - JAX DevOps London (20)

More from Henning Jacobs (20)

Recently uploaded (20)

Optimizing Kubernetes Resource Requests/Limits for Cost-Efficiency and Latency - JAX DevOps London