opentelemetry-rust/stress
Anton Grübel 8c29ca7e21
chore: leverage fallback resolver for MSRV check (#2993)
2025-05-22 08:39:53 -07:00
..
src feat: add shutdown with timeout for traces (#2956) 2025-05-16 07:12:50 -07:00
Cargo.toml chore: leverage fallback resolver for MSRV check (#2993) 2025-05-22 08:39:53 -07:00
README.md Use as many threads as logical cores for achieving full utilization (#1897) 2024-06-27 13:25:04 -07:00

README.md

OpenTelemetry Stress Tests

Why would you need stress test

  • It helps you to understand performance.
  • You can keep it running for days and nights to verify stability.
  • You can use it to generate lots of load to your backend system.
  • You can use it with other stress tools (e.g. a memory limiter) to verify how your code reacts to certain resource constraints.

Usage

Open a console, run the following command from the current directory:

cargo run --release --bin X

where X is the specific stress test you would like to run.

e.g.

cargo run --release --bin metrics

Press (Ctrl + C) to quit the tests.

Example output:

Number of threads: 4
Throughput: 4,714,600 iterations/sec
Throughput: 4,840,200 iterations/sec
Throughput: 3,905,200 iterations/sec
Throughput: 4,106,600 iterations/sec
Throughput: 5,075,400 iterations/sec

Feature flags

"stats" - Prints memory and CPU usage. Has slight impact on throughput.

cargo run --release --bin metrics --features=stats