Performance Testing Tonic - WIP
A normal workflow for grpc/tonic deployments:
1) compile the protobuf files,
2) build the source code,
3) deploy the application components to 1 or more hosts
The sub-directories here contain samples supporting that process, specifically for testing tonic.
A simple client/server test of tonic can be found in client_and_server.rs and run with: cargo run --bin hellotonic-pair
This directory is an experiment aimed at getting a consistent baseline environment with some configurable paraemters.
Rustwide is a baseline environment for building Rust crates/projects. It is used by the rust-doc project as well as Crater, a testing framework for the Rust crate eco-system.
Using rustwide for building let's us:
- Maintain a consistent build environment (a docker image),
- Easily switch out the Rust toolchain for testing,
- Easily configure different sources for building (local/github repository)
- Document a build process
There's some overlap with what cargo build and a typical CI/CD process do, so, if used, it needs to be crafted to fit your specific workflow. One useful scenario: spin up the sandboxed-tonic environment with constraints (e.g. memory) on the container to faciliate performance testing.
To pull the rustwide image, install a beta toolchain, install the rustfmt dependency of tonic, build a sandboxed image, then test by spawning a server on a separate thread and sending 1000 requests:
cargo run --bin rustwide_pair Notes -
- this pulls the rust baseline build image and an index of crates the first invocation. It will be slow.
- obviously, it's not a distributed test.
- the code it runs can be run indpendent of rustwide from the hello-tonic directory
WIP