redis/memtier_benchmark — explained in plain English
Analysis updated 2026-07-06 · repo last pushed 2026-07-02
Simulate a massive traffic spike to verify your database can handle a surge in users before a big event.
Compare the speed and latency of different server hardware or database configurations under the same workload.
Record real production database commands and replay them at scale to benchmark realistic application traffic.
Measure database response times in detail, including how long the slowest requests take to complete.
| redis/memtier_benchmark | microsoft/intelligent-terminal | zoyamalhotra/dualsensex-dsx-steam-edition | |
|---|---|---|---|
| Stars | 1,041 | 1,349 | 576 |
| Language | C++ | C++ | C++ |
| Last pushed | 2026-07-02 | 2026-07-03 | — |
| Maintenance | Active | Active | — |
| Setup difficulty | moderate | easy | easy |
| Complexity | 3/5 | 3/5 | 1/5 |
| Audience | ops devops | developer | general |
Figures from each repo's GitHub metadata at analysis time.
Needs to be compiled from C++ source and requires a running Redis or Memcached instance to test against.
memtier_benchmark is a tool that stress-tests databases to see how fast they can go and how they behave under heavy traffic. It works specifically with Redis and Memcached, two popular systems that store data in memory for quick access. If you're building an app that relies on one of these databases and want to know whether it can survive a surge of users, this tool generates a flood of read and write requests to find out. At a high level, you run it from your command line and tell it what kind of traffic to simulate. You can adjust the mix of reads versus writes, control how many requests happen per second, and even replay a recording of real traffic captured from a live database. It then measures how long each request takes to complete, giving you detailed statistics on speed and latency. Instead of just showing an average response time, it breaks down the results into percentiles, so you can see things like how long the slowest 1% of requests took. This tool is used by engineers and teams who manage database infrastructure. For example, if a retail company is preparing for a Black Friday sale and expects a massive spike in shoppers, they would use this tool to simulate that traffic beforehand. It helps them figure out if their current setup will hold up or if they need to add more servers. It is also useful for comparing different hardware or configurations to see which one performs better under the same workload. A notable feature is the ability to replay real captured traffic. You can record the actual commands your database receives in production, filter them down to a representative sample, and replay them at any scale. This means you aren't just running artificial tests, you can benchmark with a realistic mix of the exact operations your application performs. The tool also supports running tests against a single database instance or a larger cluster spread across multiple machines.
A command-line tool that stress-tests Redis and Memcached databases by simulating heavy traffic. It measures speed and response times to help you see if your database can handle surge loads.
Mainly C++. The stack also includes C++, Redis, Memcached.
Active — commit in last 30 days (last push 2026-07-02).
Use freely for any purpose, including commercial use, as long as you include the copyright notice.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.