# memtier_benchmark mit Homebrew, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für memtier_benchmark in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:memtier_benchmark
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install memtier_benchmark
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#memtier-benchmark
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/me/memtier-benchmark/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Paketfakten

- **Paketschlüssel:** brew:memtier_benchmark
- **Paketmanager:** Homebrew
- **Version:** 2.5.1
- **Quellzusammenfassung:** Redis and Memcache traffic generation and benchmarking tool
- **Homepage:** <https://github.com/redis/memtier_benchmark>
- **Repository:** <https://github.com/redis/memtier_benchmark>
- **Zuletzt aktualisiert:** 2026-07-16T12:17:17Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- memtier_benchmark (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 2.5.1
## Projektgeschichte und Nutzung

memtier_benchmark began as a Redis Labs/Garantia Data benchmarking tool for generating heavy Redis and Memcached traffic. Yiftach Shoolman announced it to the Redis DB mailing list in July 2013 as a complementary tool to redis-benchmark, noting that redis-benchmark covered only simple GET and SET workloads. Redis's own launch article described the motivation as regression testing and database-performance optimization, with the source released under GPLv2.

### Projektgeschichte

The tool's niche is realistic key-value-store load generation from a single command-line executable. It supports both Redis and Memcached protocols, multithreaded and multi-client execution, configurable read/write ratios, sequential or random key patterns, expiry ranges, Redis Cluster, and TLS. In practice, engineers use it for capacity tests, latency and throughput comparisons, performance regression checks, and synthetic workload generation before changing cache/database deployments.

### Wie es verwendet wird

Its packaging footprint reflects that role: it is distributed as Redis-provided APT/YUM packages, a Homebrew formula, and a Nix package. The Phoronix Test Suite added a memtier_benchmark profile in 2019, making it part of reusable public benchmark workflows as well as Redis-oriented operations work.

### Quellen

- <https://github.com/redis/memtier_benchmark>
- <https://groups.google.com/g/redis-db/c/aPFyn8jLFTs>
- <https://openbenchmarking.org/test/pts/memtier-benchmark-1.5.0>
- <https://redis.io/blog/memtier_benchmark-a-high-throughput-benchmarking-tool-for-redis-memcached/>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals

## Andere Paketmanager-Einträge

- Nix - memtier-benchmark: normalized package name match | nixpkgs package indexes: pkgs/by-name/me/memtier-benchmark/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

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


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph