https://rancher.com/ logo
Title
l

lively-wolf-56294

05/02/2023, 12:49 PM
There are a lot of High CPU use issues reported in GitHub. I sympathize with this latest post https://canthonyscott.com/k3s-cpu-usage-bug-remains/. Most of my tests are on arm64 (RockPi 4). I have tested versions from v1.24.x until v1.27.1. The use case is very simple: just start
k3s.service
and
k3s-server
takes >50% of CPU and a good chunk of RAM too.
k3s check-config
passes. Checked the k3s logs but it looks normal to me. What else could be done to address the High CPU use on arm64?
1
Installing k3s using the steps from web page:
curl -sfL <https://get.k3s.io> | sh - 
# Check for Ready node, takes ~30 seconds 
sudo k3s kubectl get node
c

clever-air-65544

05/02/2023, 4:34 PM
You've linked a list with 89 closed bugs, 5 open
RockPi is a very low powered device, kubernetes is a pretty big resource hog, the fact that it's runnable on k3s highights that it is in fact lightweight
l

lively-wolf-56294

05/02/2023, 5:08 PM
Hi Chris, thank you for replying to my post. Which arm64 HW do you recommend to run k3s?
from the official k3s installation is possible to install k3s with debug symbols to profile which part of the code is consuming the CPU?
c

creamy-pencil-82913

05/02/2023, 9:05 PM
and no, we do not ship a version with extra symbols because that’s not generally how one profiles golang, but we do have a flag to enable pprof.
👍 1
l

lively-wolf-56294

05/02/2023, 9:30 PM
Those links clarify and answer my questions. Thank you so much for taking your time to look and share it!