perf-tests | Performance tests and benchmarks | Runtime Evironment library

 by   kubernetes Go Version: Current License: Apache-2.0

kandi X-RAY | perf-tests Summary

kandi X-RAY | perf-tests Summary

perf-tests is a Go library typically used in Server, Runtime Evironment, React, Nodejs, Nginx applications. perf-tests has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

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.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              perf-tests has a medium active ecosystem.
              It has 768 star(s) with 465 fork(s). There are 39 watchers for this library.
              OutlinedDot
              It had no major release in the last 6 months.
              There are 57 open issues and 302 have been closed. On average issues are closed in 201 days. There are 14 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of perf-tests is current.

            kandi-Quality Quality

              perf-tests has no bugs reported.

            kandi-Security Security

              perf-tests has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

            kandi-License License

              perf-tests is licensed under the Apache-2.0 License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              perf-tests releases are not available. You will need to build from source code and install.
              Installation instructions, examples and code snippets are available.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of perf-tests
            Get all kandi verified functions for this library.

            perf-tests Key Features

            No Key Features are available at this moment for perf-tests.

            perf-tests Examples and Code Snippets

            No Code Snippets are available at this moment for perf-tests.

            Community Discussions

            QUESTION

            how to test performance of kubernetes cluster network?
            Asked 2019-Oct-03 at 09:39

            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.

            ...

            ANSWER

            Answered 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.

            Source https://stackoverflow.com/questions/58200414

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install perf-tests

            To run all verify* scripts before pushing to remote branch (useful for catching problems quickly) execute:.

            Support

            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/kubernetes/perf-tests.git

          • CLI

            gh repo clone kubernetes/perf-tests

          • sshUrl

            git@github.com:kubernetes/perf-tests.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link