redis
Database
Redis latency
Running a pair of redis server and benchmarking client (memtier_benchmarkmemtier_benchmarkAn open-source load generator for Redis and Memcached, developed by Redis Ltd. It runs many concurrent connections over one or more threads, sends a configurable mix of SET and GET requests, and reports operations per second, latency averages, and latency percentiles per request type.memtier_benchmark on GitHubGlossary) on each vCPUvCPU: virtual CPUA CPU of a virtual machine, the unit in which cloud vendors sell compute. It is usually one hardware thread of a physical core with SMT, so two vCPUs may share one physical core.WikipediaGlossary to evaluate the performance of SET operations, using different number of concurrent pipelined requests. The average latency reported by memtier_benchmark.
Benchmark details
- Benchmark ID
redis:latency- Unit of measurement
- Milliseconds (ms)
- Server types evaluated
- 3,720
- Total measurements
- 22,320
- Range of measurements
- 0.25 – 750.7 ms
- Better
- ↓ Lower is better
Configuration options
| Field | Description | Example values |
|---|---|---|
pipeline | The number of concurrent pipelined requests. | 1 4 16 64 256 512 |
operation | Type of operation, e.g. SET or GET a key. | SET |
Latency is recorded during the redis:rps run, not as a standalone benchmark. As it reflects a characteristic of that throughput measurement, it is not recommended for comparing instances on its own; use it instead as a filter when interpreting the related throughput scores.
Score distribution (22,320 measurements)
Redis server+client speed
Running a pair of redis server and benchmarking client (memtier_benchmarkmemtier_benchmarkAn open-source load generator for Redis and Memcached, developed by Redis Ltd. It runs many concurrent connections over one or more threads, sends a configurable mix of SET and GET requests, and reports operations per second, latency averages, and latency percentiles per request type.memtier_benchmark on GitHubGlossary) on each vCPU to evaluate the performance of SET operations, using different number of concurrent pipelined requests. The measured RPS (ops/sec) is the sum of RPS measured in all parallel processes, but is not the maximum expected redis server speed, as the server(s) share CPUCPU: Central Processing UnitThe general-purpose processor of a computer, which runs the operating system and programs. A CPU has one or more physical cores, and with SMT each core runs two or more hardware threads.WikipediaGlossary with the client(s).
Benchmark details
- Benchmark ID
redis:rps- Unit of measurement
- Operations per second (ops/sec)
- Server types evaluated
- 3,720
- Total measurements
- 22,320
- Range of measurements
- 5K – 254.8M ops/sec
- Better
- ↑ Higher is better
Configuration options
| Field | Description | Example values |
|---|---|---|
pipeline | The number of concurrent pipelined requests. | 1 4 16 64 256 512 |
operation | Type of operation, e.g. SET or GET a key. | SET |
Score distribution (22,320 measurements)
Redis server (extrapolated) speed
Running a pair of redis server and benchmarking client (memtier_benchmarkmemtier_benchmarkAn open-source load generator for Redis and Memcached, developed by Redis Ltd. It runs many concurrent connections over one or more threads, sends a configurable mix of SET and GET requests, and reports operations per second, latency averages, and latency percentiles per request type.memtier_benchmark on GitHubGlossary) on each vCPU to evaluate the performance of SET operations, using different number of concurrent pipelined requests. The extrapolated server speed is based on the measured speed adjusted by the server's and client's time spent executing in user/system mode, so trying to control for the client resource usage.
Benchmark details
- Benchmark ID
redis:rps-extrapolated- Unit of measurement
- Operations per second (ops/sec)
- Server types evaluated
- 3,720
- Total measurements
- 22,320
- Range of measurements
- 10.5K – 555.7M ops/sec
- Better
- ↑ Higher is better
Derived from redis:rps: Measured RPS adjusted by server/client user+system CPU time to control for client resource usage.
Configuration options
| Field | Description | Example values |
|---|---|---|
pipeline | The number of concurrent pipelined requests. | 1 4 16 64 256 512 |
operation | Type of operation, e.g. SET or GET a key. | SET |
Score distribution (22,320 measurements)