# Install benchi with Homebrew Benchmarking tool for data pipelines. Version 0.4.1 via Homebrew; verified from local package data. ## 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 - **Package manager page:** - **Version:** 0.4.1 - **Source summary:** Benchmarking tool for data pipelines - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** Apache-2.0 - **Source archive:** - **Generated:** 2026-07-10T07:20:53+00:00 ## Executables - benchi (cli) - benchi (alias) ## Build dependencies - go ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux ## Freshness - Page generated: 2026-07-10 - Package-manager version: 0.4.1 - Local data: ok - Upstream repository: https://github.com/ConduitIO/benchi - Upstream latest detected: v0.4.1 (current) - info: No package-manager update timestamp was available. ## 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 ` 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 - - - 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 ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** benchi - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Related links - [Source-control packages](https://www.automicvault.com/pkg/source-control-tools/) - Belongs to a source-control command family. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [go](https://www.automicvault.com/pkg/brew/go/) - Build dependency declared by Homebrew. - [ali](https://www.automicvault.com/pkg/brew/ali/) - Shares av.db curated category or tags: benchmark, cli, developer-tools. - [apib](https://www.automicvault.com/pkg/brew/apib/) - Shares av.db curated category or tags: benchmark, cli, developer-tools. - [autobench](https://www.automicvault.com/pkg/brew/autobench/) - Shares av.db curated category or tags: benchmark, cli, developer-tools. - [autocannon](https://www.automicvault.com/pkg/brew/autocannon/) - Shares av.db curated category or tags: benchmark, cli, developer-tools. - [hey](https://www.automicvault.com/pkg/brew/hey/) - Shares av.db curated category or tags: benchmark, cli, developer-tools. - [memtier_benchmark](https://www.automicvault.com/pkg/brew/memtier-benchmark/) - Shares av.db curated category or tags: benchmark, cli, developer-tools. - [nanobench](https://www.automicvault.com/pkg/npm/nanobench/) - Local package facts share a topical domain. Shared terms: benchmark, benchmarking, cli, developer, developer-tools. ## Combined YAML source View the package source record on GitHub. [combined/benchi.yml](https://github.com/automic-vault/db/blob/main/combined/benchi.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - cross-ecosystem install command graph