You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: contributors/devel/sig-node/node-performance-testing.md
+18-3Lines changed: 18 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ must be taken in setting up the cluster to make the intended measurements. In
10
10
addition to taking the following steps into consideration, it is important to
11
11
document precisely which setup was used. For example, performance can vary
12
12
wildly from commit-to-commit, so it is very important to **document which commit
13
-
or version** of Kubernetes was used, which Docker version was used, etc.
13
+
or version** of Kubernetes was used, which container runtime version was used, etc.
14
14
15
15
### Addon pods
16
16
@@ -54,18 +54,33 @@ environment etc. with a single node to worry about. On the other hand, having
54
54
multiple nodes will let you gather more data in parallel for more robust
55
55
sampling.
56
56
57
-
## E2E Performance Test
57
+
## Performance Dashboard
58
+
Since Kubernetes release 1.22 kubelet resource usage is also being tracked via [k8s performance dashboard](http://perf-dash.k8s.io/).
58
59
60
+
## E2E Performance Test
59
61
There is an end-to-end test for collecting overall resource usage of node
60
62
components: [kubelet_perf.go](https://git.k8s.io/kubernetes/test/e2e/node/kubelet_perf.go). To
61
63
run the test, simply make sure you have an e2e cluster running (`kubetest --up`) and [set up](#cluster-set-up) correctly.
62
64
63
65
Run the test with `kubetest --test --test_args="--ginkgo.focus=resource\susage\stracking"`. You may also wish to customise the number of pods or other parameters of the test (remember to rerun
64
66
`make WHAT=test/e2e/e2e.test` after you do).
65
67
68
+
Note: Due to the amount of time those tests consume they are not currently running in CI, see [issue](https://github.com/kubernetes/kubernetes/issues/81490).
69
+
70
+
## Node E2E Peformance Test
71
+
These node e2e tests measure node performance after deploying performance sensitive workloads.
To run theses tests follow [node e2e setup guide](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/e2e-node-tests.md) and run
Kubelet installs the [go pprof handlers](https://golang.org/pkg/net/http/pprof/), which can be queried for CPU profiles:
82
+
Kubelet installs the [go pprof handlers](https://golang.org/pkg/net/http/pprof/), which can be queried for CPU profiles.
83
+
To enable the pprof endpint for kubelet pass `--enable-debugging-handlers=true` as kubelet flag or `EnableDebuggingHandlers=true` as a kubelet configuration option.
0 commit comments