kandi X-RAY | perf-tests Summary
kandi X-RAY | perf-tests Summary
This repo is dedicated for storing various Kubernetes-related performance test related tools. If you want to add your own load-test, benchmark, framework or other tool please contact with one of the Owners. Because in general tools are independent and have their own ways of being configured or run, each subdirectory needs a separate README.md file with the description of its contents.
Top functions reviewed by kandi - BETA
perf-tests Key Features
perf-tests Examples and Code Snippets
Trending Discussions on perf-tests
I've a kubernetes cluster in aws, created with kops. I'm trying to evaluate network performance of the kubernetes cluster. I'm using default kubernetes CNI kubenet....
ANSWERAnswered 2019-Oct-03 at 09:39
This script is testing iperf/netperf transfer speed in MSS testpoint in 5 scenarios for TCP, UDP and NetPerf.
Honestly all you have described in provided Github links.
Iperf is a commonly used network testing tool that can create TCP/UDP data streams and measure the throughput of a network that is carrying them. It allows the user to set various parameters that can be used for testing a network, or alternatively for optimizing or tuning a network.
Netperf is also another good network testing tool, which is also used by the PerfKitBenchmark suite to test performance and benchmark the various cloud providers to each other.
More information you can find here
On the Github you have 2x5 ipetf scenarios for TCP and UPD and 5 scenarios for netperf.
The 5 major network traffic paths are combination of Pod IP vs Virtual IP and whether the pods are co-located on the same node/VM versus a remotely located pod.
- Same VM using Pod IP
Same VM Pod to Pod traffic tests from Worker 1 to Worker 2 using its Pod IP.
- Same VM using Cluster/Virtual IP
Same VM Pod to Pod traffic tests from Worker 1 to Worker 2 using its Service IP (also known as its Cluster IP or Virtual IP).
- Remote VM using Pod IP
Worker 3 to Worker 2 traffic tests using Worker 2 Pod IP.
- Remote VM using Cluster/Virtual IP
Worker 3 to Worker 2 traffic tests using Worker 2 Cluster/Virtual IP.
- Same VM Pod Hairpin to itself using Cluster IP
Regarding CSV output
MMS - Maximum Segment Size. More information about it can be found here.
Example TCP MMS The TCP protocol includes a mechanism for both ends of a connection to negotiate the maximum segment size (MSS) to be used over the connection. Each end uses the OPTIONS field in the TCP header to advertise a proposed MSS. The MSS that is chosen is the smaller of the values provided by the two ends.
The purpose of this negotiation is to avoid the delays and throughput reductions caused by fragmentation of the packets when they pass through routers or gateways and reassembly at the destination host.
The value of MSS advertised by the TCP software during connection setup depends on whether the other end is a local system on the same physical network (that is, the systems have the same network number) or whether it is on a different (remote) network.
So for each scenario (Maximum Segment Size), for protocol, script is measuring transfer speed per MSS datapoint in Mbit/sec. This output will have better visibility if you paste it to excel and use "Text to Columns" divided by comma.
In graph you have the same values, just for better visibility.
No vulnerabilities reported
Reuse Trending Solutions
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page