envoyproxy/envoy-perf

Envoy performance testing

146

stars

196

commits

Python

primary language

Sep 10, 2026

updated

envoyproxy.io
benchmarking
cncf
envoy

README

Envoy performance tools collection

OpenSSF Scorecard

Performance benchmarking Options

Performance benchmarking can take multiple forms:

  1. relatively quick (< 1 hour) tests to run locally during development to understand perf impact of changes
  2. continuous dashboard of perf changes over time, covering a variety of realistic deployment scenarios with multiple machines and configurations
  3. continuous-integration tests to prevent checking in performance regressions -- similar to coverage tests

Subdirectories

  1. cloudperf/ contains what appears to be an attempt at measuring performance in a realistic multi-machine scenario. However, the instructions don't work, and it hasn't been touched in a year (other than moving the files).
  2. siege/ contains an initial attempt at a simple test to run iteratively during development to get a view of the time/space impact of the changes under configuration.
  3. salvo/ contains a framework that abstracts nighthawk benchmark execution. This is still under active development

Contributors

dependabot[bot]

76 commits

abaptiste

31 commits

mum4k

29 commits

oschaaf

18 commits

envoyproxy/envoy-perf

Envoy performance testing

146

stars

196

commits

Python

primary language

Sep 10, 2026

updated

envoyproxy.io
benchmarking
cncf
envoy

README

Envoy performance tools collection

OpenSSF Scorecard

Performance benchmarking Options

Performance benchmarking can take multiple forms:

  1. relatively quick (< 1 hour) tests to run locally during development to understand perf impact of changes
  2. continuous dashboard of perf changes over time, covering a variety of realistic deployment scenarios with multiple machines and configurations
  3. continuous-integration tests to prevent checking in performance regressions -- similar to coverage tests

Subdirectories

  1. cloudperf/ contains what appears to be an attempt at measuring performance in a realistic multi-machine scenario. However, the instructions don't work, and it hasn't been touched in a year (other than moving the files).
  2. siege/ contains an initial attempt at a simple test to run iteratively during development to get a view of the time/space impact of the changes under configuration.
  3. salvo/ contains a framework that abstracts nighthawk benchmark execution. This is still under active development

Contributors

dependabot[bot]

76 commits

abaptiste

31 commits

mum4k

29 commits

oschaaf

18 commits

Languages

Python

76.0%

Go

10.7%

Shell

6.0%

HCL

3.5%

Starlark

3.5%