# Install benchi with Homebrew

Benchmarking tool for data pipelines. Version 0.4.1 via Homebrew; verified 2026-07-26.

## Install

```sh
sudo av install brew:benchi
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install benchi
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:benchi
- **Package manager:** Homebrew
- **Version:** 0.4.1
- **Source summary:** Benchmarking tool for data pipelines
- **Homepage:** <https://github.com/ConduitIO/benchi>
- **Repository:** <https://github.com/ConduitIO/benchi>
- **Last updated:** 2026-07-26T10:56:33+02:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- benchi (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 0.4.1
## Project history and usage

Benchi is ConduitIO's minimal Docker-based benchmarking framework for measuring application and infrastructure performance, especially data-pipeline scenarios.

### Project history

The official repository was created in February 2025. The README says Benchi was developed to simplify setting up and running benchmarks for Conduit, and describes Docker Compose environments, metrics collection, hooks, and real-time monitoring.

Public releases moved quickly in March and April 2025, from v0.1.0 through v0.4.1, giving the project a compact early release history rather than a long legacy.

### Adoption history

Benchi's adoption story is currently tied to the Conduit ecosystem and Go/Docker users. The README documents binary downloads, `go install`, and a shell installer, while the supplied Homebrew facts show package-manager availability.

Because it is young and specialized, its public adoption is better described as early ecosystem packaging than broad industry uptake.

### How it is used

Users run `benchi -config <file>` against a YAML benchmark configuration that defines Docker Compose infrastructure, tools, metrics collectors, tests, and lifecycle hooks. Results are written into timestamped output directories with logs and aggregated CSV metrics.

The tool is suited to repeatable infrastructure benchmarks where containers, Prometheus-like metrics, and scripted benchmark phases matter more than single-command timing.

### Why package nerds care

Benchi is package-nerd interesting as a young, purpose-built benchmark harness for containerized data infrastructure. It packages a repeatable benchmark workflow, not just a timer.

Its significance is still emerging; the reason to care today is that it turns Conduit-style pipeline benchmarking into a small installable CLI.

### Timeline

- 2025: Repository created.
- 2025: v0.1.0 released.
- 2025: v0.4.1 released.
- 2025: Homebrew package metadata lists `benchi` as an installable formula.

### Related projects

- Conduit is the data-pipeline project Benchi was developed to benchmark.
- Docker Compose is central to Benchi's benchmark environment model.
- Prometheus-style metrics endpoints are used by documented collector examples.

### Sources

- <https://github.com/ConduitIO/benchi>
- <https://github.com/ConduitIO/benchi/releases>
- source_facts.package-manager-url
- source_facts.repo


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: path passed to benchi -config

## Combined YAML source

View the package source record on GitHub. [combined/benchi.yml](https://github.com/mxcl/pkgdb/blob/main/combined/benchi.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph