Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update linux.md to fix some typos #20312

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 13 additions & 13 deletions site/content/en/docs/benchmarks/cpuUsage/linux.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,8 +10,8 @@ This chart shows each tool's CPU busy overhead percentage.
After each tool's starting, we measured each tool's idle for 5 minutes.
This chart was measured only after the start without deploying any pods.

1. start each local kubernetes tool
2. measure its cpu usage with [cstat](https://github.com/tstromberg/cstat)
1. Start each local kubernetes tool
2. Measure its CPU usage with [cstat](https://github.com/tstromberg/cstat)

![idleOnly](/images/benchmarks/cpuUsage/idleOnly/linux.png)

Expand All @@ -20,23 +20,23 @@ https://cloud.google.com/compute/docs/instances/enable-nested-virtualization-vm-

## CPU% Busy Overhead - With Auto Pause vs. Non Auto Pause

This chart shows each tool's CPU busy overhead percentage with auto-pause addon.
The auto-pause is mechanism which reduce CPU busy usage by pausing kube-apiserver.
We compare CPU usage after deploying sample application (nginx deployment) to all tools (including minikube and other tools).
This chart was measured with the following steps.
By these steps, we compare CPU usage with auto-pause vs. non-auto-pause.
This chart shows each tool's CPU busy overhead percentage with the auto-pause addon, which reduces the CPU's busy usage by pausing the kube-apiserver.
We compare CPU usage after deploying a sample application (nginx deployment) to all tools (including minikube and other tools).

We followed these steps to compare the CPU's usage with auto-pause vs. non-auto-pause:

1. start each local kubernetes tool
2. deploy sample application (nginx deployment) to each tool
2. deploy the sample application (nginx deployment) to each tool
3. wait 1 minute without anything
4. measure No.3 idle CPU usage with [cstat](https://github.com/tstromberg/cstat)
5. if tool is minikube, enable auto-pause addon which pause control plane
6. if tool is minikube, wait 1 minute so that control plane will become Paused status (It takes 1 minute to become Pause status from Stopped status)
7. if tool is minikube, verify if minikube control plane is paused
8. if tool is minikube, wait 3 minute without anything
9. if tool is minikube, measure No.8 idle CPU usage with [cstat](https://github.com/tstromberg/cstat)
5. if the tool is minikube, enable auto-pause addon which will pause the control plane
6. if the tool is minikube, wait 1 minute so that control plane will change its status to Paused (It takes 1 minute for the Paused status to change from the Stopped status)
7. if the tool is minikube, verify if minikube control plane is paused
8. if the tool is minikube, wait 3 minute without anything
9. if the tool is minikube, measure No.8 idle CPU usage with [cstat](https://github.com/tstromberg/cstat)

No.1-4: Initial start CPU usage with sample (nginx) deployment

No.5-9: Auto Paused CPU usage with sample (nginx) deployment

![autopause](/images/benchmarks/cpuUsage/autoPause/linux.png)
Expand Down