利用redis-benchmark 对redis服务做简单压测
1. 查看redis-benchmark帮助文档
root@node130:/redises/s0/bin# ls
redis-benchmark redis-check-aof redis-check-rdb redis-cli redis.pid redis-sentinel redis-server
root@node130:/redises/s0/bin# ./redis-benchmark --help
Usage: redis-benchmark [-h <host>] [-p <port>] [-c <clients>] [-n <requests>] [-k <boolean>]
-h <hostname> Server hostname (default 127.0.0.1)
-p <port> Server port (default 6379)
-s <socket> Server socket (overrides host and port)
-a <password> Password for Redis Auth
-c <clients> Number of parallel connections (default 50)
-n <requests> Total number of requests (default 100000)
-d <size> Data size of SET/GET value in bytes (default 3)
--dbnum <db> SELECT the specified db number (default 0)
-k <boolean> 1=keep alive 0=reconnect (default 1)
-r <keyspacelen> Use random keys for SET/GET/INCR, random values for SADD
Using this option the benchmark will expand the string __rand_int__
inside an argument with a 12 digits number in the specified range
from 0 to keyspacelen-1. The substitution changes every time a command
is executed. Default tests use this to hit random keys in the
specified range.
-P <numreq> Pipeline <numreq> requests. Default 1 (no pipeline).
-e If server replies with errors, show them on stdout.
(no more than 1 error per second is displayed)
-q Quiet. Just show query/sec values
--csv Output in CSV format
-l Loop. Run the tests forever
-t <tests> Only run the comma separated list of tests. The test
names are the same as the ones produced as output.
-I Idle mode. Just open N idle connections and wait.
Examples:
Run the benchmark with the default configuration against 127.0.0.1:6379:
$ redis-benchmark
Use 20 parallel clients, for a total of 100k requests, against 192.168.1.1:
$ redis-benchmark -h 192.168.1.1 -p 6379 -n 100000 -c 20
Fill 127.0.0.1:6379 with about 1 million keys only using the SET test:
$ redis-benchmark -t set -n 1000000 -r 100000000
Benchmark 127.0.0.1:6379 for a few commands producing CSV output:
$ redis-benchmark -t ping,set,get -n 100000 --csv
Benchmark a specific command line:
$ redis-benchmark -r 10000 -n 10000 eval 'return redis.call("ping")' 0
Fill a list with 10000 random elements:
$ redis-benchmark -r 10000 -n 10000 lpush mylist __rand_int__
On user specified command
2. 中文参数解释
参数 | 中文描述 | 默认值 |
-h | 指定服务器主机名 | 127.0.0.1 |
-p | 指定服务器端口 | 6379 |
-s | 指定服务器的socket | |
-c | 指定并发连接数 | 50 |
-n | 指定请求数 | 10000 |
-d | 以字节的形式指定 set/get值的数据大小 | |
-k | 1=keep alive 0=reconnect | 1 |
-r | set/get/incr 使用随机key,sadd 使用随机值 | |
-P | 通过管道传输 请求 | |
-q | 强制退出 redis. 仅显示 query/sec值 | |
–csv | 以csv格式输出 | |
-l | 生成循环，永久执行测试 | |
-t | 仅运行以逗号分隔的测试命令列表 | |
-I | idel模式， 仅仅打开N个idle链接并等待 |
3. 测试命令
# ./redis-benchmark -h 127.0.0.1 -p 6379 -c 50 -n 10000
====== PING_INLINE ======
10000 requests completed in 0.28 seconds
50 parallel clients
3 bytes payload
keep alive: 1
97.43% <= 1 milliseconds
99.50% <= 2 milliseconds
99.51% <= 28 milliseconds
99.55% <= 29 milliseconds
99.80% <= 30 milliseconds
100.00% <= 30 milliseconds
35460.99 requests per second
====== PING_BULK ======
10000 requests completed in 0.24 seconds
50 parallel clients
3 bytes payload
keep alive: 1
97.80% <= 1 milliseconds
100.00% <= 1 milliseconds
41493.78 requests per second
====== SET ======
10000 requests completed in 0.30 seconds
50 parallel clients
3 bytes payload
keep alive: 1
91.40% <= 1 milliseconds
99.42% <= 2 milliseconds
99.60% <= 3 milliseconds
99.90% <= 4 milliseconds
100.00% <= 4 milliseconds
33444.82 requests per second
====== GET ======
10000 requests completed in 0.31 seconds
50 parallel clients
3 bytes payload
keep alive: 1
91.68% <= 1 milliseconds
99.92% <= 2 milliseconds
100.00% <= 2 milliseconds
32786.88 requests per second
====== INCR ======
10000 requests completed in 0.32 seconds
50 parallel clients
3 bytes payload
keep alive: 1
93.29% <= 1 milliseconds
100.00% <= 1 milliseconds
31250.00 requests per second
====== LPUSH ======
10000 requests completed in 0.32 seconds
50 parallel clients
3 bytes payload
keep alive: 1
92.83% <= 1 milliseconds
100.00% <= 1 milliseconds
31152.65 requests per second
====== RPUSH ======
10000 requests completed in 0.32 seconds
50 parallel clients
3 bytes payload
keep alive: 1
92.29% <= 1 milliseconds
99.76% <= 2 milliseconds
100.00% <= 2 milliseconds
31152.65 requests per second
====== LPOP ======
10000 requests completed in 0.31 seconds
50 parallel clients
3 bytes payload
keep alive: 1
92.29% <= 1 milliseconds
100.00% <= 1 milliseconds
32154.34 requests per second
====== RPOP ======
10000 requests completed in 0.31 seconds
50 parallel clients
3 bytes payload
keep alive: 1
92.80% <= 1 milliseconds
100.00% <= 1 milliseconds
32258.06 requests per second
====== SADD ======
10000 requests completed in 0.31 seconds
50 parallel clients
3 bytes payload
keep alive: 1
92.78% <= 1 milliseconds
100.00% <= 1 milliseconds
31948.88 requests per second
====== HSET ======
10000 requests completed in 0.30 seconds
50 parallel clients
3 bytes payload
keep alive: 1
93.77% <= 1 milliseconds
100.00% <= 1 milliseconds
33112.59 requests per second
====== SPOP ======
10000 requests completed in 0.31 seconds
50 parallel clients
3 bytes payload
keep alive: 1
90.78% <= 1 milliseconds
99.32% <= 2 milliseconds
100.00% <= 2 milliseconds
32786.88 requests per second
====== LPUSH (needed to benchmark LRANGE) ======
10000 requests completed in 0.31 seconds
50 parallel clients
3 bytes payload
keep alive: 1
91.02% <= 1 milliseconds
100.00% <= 1 milliseconds
32467.53 requests per second
====== LRANGE_100 (first 100 elements) ======
10000 requests completed in 0.30 seconds
50 parallel clients
3 bytes payload
keep alive: 1
92.54% <= 1 milliseconds
100.00% <= 1 milliseconds
33112.59 requests per second
====== LRANGE_300 (first 300 elements) ======
10000 requests completed in 0.30 seconds
50 parallel clients
3 bytes payload
keep alive: 1
90.91% <= 1 milliseconds
99.74% <= 2 milliseconds
100.00% <= 2 milliseconds
33783.79 requests per second
====== LRANGE_500 (first 450 elements) ======
10000 requests completed in 0.31 seconds
50 parallel clients
3 bytes payload
keep alive: 1
83.07% <= 1 milliseconds
97.92% <= 2 milliseconds
99.84% <= 3 milliseconds
99.94% <= 4 milliseconds
100.00% <= 4 milliseconds
32467.53 requests per second
====== LRANGE_600 (first 600 elements) ======
10000 requests completed in 0.31 seconds
50 parallel clients
3 bytes payload
keep alive: 1
90.49% <= 1 milliseconds
99.59% <= 2 milliseconds
100.00% <= 2 milliseconds
32786.88 requests per second
====== MSET (10 keys) ======
10000 requests completed in 0.38 seconds
50 parallel clients
3 bytes payload
keep alive: 1
2.39% <= 1 milliseconds
79.97% <= 2 milliseconds
99.93% <= 3 milliseconds
100.00% <= 3 milliseconds
26041.67
root@node130:/redises/s0/bin# ./redis-benchmark -h 127.0.0.1 -p 6379 -c 1 -n 1000 -t get
====== GET ======
1000 requests completed in 0.06 seconds
1 parallel clients
3 bytes payload
keep alive: 1
100.00% <= 0 milliseconds
17543.86 requests per second
root@node130:/redises/s0/bin# ./redis-benchmark -h 127.0.0.1 -p 6379 -c 1 -n 1000 -t set
====== SET ======
1000 requests completed in 0.06 seconds
1 parallel clients
3 bytes payload
keep alive: 1
100.00% <= 0 milliseconds
17857.14 requests per second
root@node130:/redises/s0/bin# ./redis-benchmark -h 127.0.0.1 -p 6379 -c 1 -n 1000 -q
PING_INLINE: 16393.44 requests per second
PING_BULK: 16949.15 requests per second
SET: 16129.03 requests per second
GET: 16666.67 requests per second
INCR: 16129.03 requests per second
LPUSH: 16129.03 requests per second
RPUSH: 15873.02 requests per second
LPOP: 15873.02 requests per second
RPOP: 16129.03 requests per second
SADD: 14285.71 requests per second
HSET: 14492.75 requests per second
SPOP: 14492.75 requests per second
LPUSH (needed to benchmark LRANGE): 14705.88 requests per second
LRANGE_100 (first 100 elements): 14492.75 requests per second
LRANGE_300 (first 300 elements): 14285.71 requests per second
LRANGE_500 (first 450 elements): 13698.63 requests per second
LRANGE_600 (first 600 elements): 14285.71 requests per second
MSET (10 keys): 11904.76