Redis-benchmark是官方自带的Redis性能测试工具，可以有效的测试Redis服务的性能。

使用说明如下：

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)-c <clients>       Number of parallel connections (default 50)-n <requests>      Total number of requests (default 10000)-d <size>          Data size of SET/GET value in bytes (default 2)-k <boolean>       1=keep alive 0=reconnect (default 1)-r <keyspacelen>   Use random keys for SET/GET/INCR, random values for SADDUsing this option the benchmark will get/set keysin the form mykey_rand:000000012456 instead of constantkeys, the <keyspacelen> argument determines the maxnumber of values for the random number. For instanceif set to 10 only rand:000000000000 - rand:000000000009range will be allowed.-P <numreq>        Pipeline <numreq> requests. Default 1 (no pipeline).-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 testnames are the same as the ones produced as output.-I                 Idle mode. Just open N idle connections and wait.

测试命令事例：

1、redis-benchmark -h 192.168.1.201 -p 6379 -c 100 -n 100000
100个并发连接，100000个请求，检测host为localhost 端口为6379的redis服务器性能

2、redis-benchmark -h 192.168.1.201 -p 6379 -q -d 100

测试结果：

测试存取大小为100字节的数据包的性能

3、redis-benchmark -t set,lpush -n 100000 -q

只测试某些操作的性能

4、redis-benchmark -n 100000 -q script load "redis.call('set','foo','bar')"

只测试某些数值存取的性能

测试结果分析：

 [root@localhost local]# ps -ef|grep redis
root       1890      1  0 18:38 ?        00:02:10 /usr/local/bin/redis-server 0.0.0.0:6379
root       3498   3294  0 22:30 pts/1    00:00:00 grep redis
[root@localhost local]# redis-benchmark -h 192.168.0.106 -p 6379 -c 100 -n 100000
====== PING_INLINE ======100000 requests completed in 0.82 seconds100 parallel clients3 bytes payloadkeep alive: 199.03% <= 1 milliseconds
99.60% <= 2 milliseconds
99.68% <= 3 milliseconds
99.77% <= 4 milliseconds
99.79% <= 6 milliseconds
99.81% <= 7 milliseconds
99.90% <= 8 milliseconds
99.90% <= 10 milliseconds
100.00% <= 10 milliseconds
121654.50 requests per second====== PING_BULK ======100000 requests completed in 0.82 seconds100 parallel clients3 bytes payloadkeep alive: 199.89% <= 1 milliseconds
100.00% <= 1 milliseconds
122249.38 requests per second====== SET ======100000 requests completed in 0.87 seconds100 parallel clients3 bytes payloadkeep alive: 199.38% <= 1 milliseconds
99.59% <= 3 milliseconds
99.65% <= 4 milliseconds
99.68% <= 6 milliseconds
99.69% <= 7 milliseconds
99.72% <= 14 milliseconds
99.75% <= 15 milliseconds
99.82% <= 18 milliseconds
99.90% <= 19 milliseconds
99.94% <= 20 milliseconds
100.00% <= 20 milliseconds
114810.56 requests per second====== GET ======100000 requests completed in 0.83 seconds100 parallel clients3 bytes payloadkeep alive: 199.89% <= 1 milliseconds
100.00% <= 1 milliseconds
120918.98 requests per second====== INCR ======100000 requests completed in 0.82 seconds100 parallel clients3 bytes payloadkeep alive: 199.96% <= 1 milliseconds
100.00% <= 1 milliseconds
121506.68 requests per second====== LPUSH ======100000 requests completed in 0.83 seconds100 parallel clients3 bytes payloadkeep alive: 199.47% <= 1 milliseconds
99.68% <= 2 milliseconds
99.88% <= 3 milliseconds
99.97% <= 4 milliseconds
100.00% <= 5 milliseconds
100.00% <= 5 milliseconds
120481.93 requests per second====== RPUSH ======100000 requests completed in 0.82 seconds100 parallel clients3 bytes payloadkeep alive: 199.87% <= 1 milliseconds
100.00% <= 1 milliseconds
122100.12 requests per second====== LPOP ======100000 requests completed in 0.83 seconds100 parallel clients3 bytes payloadkeep alive: 199.93% <= 1 milliseconds
100.00% <= 1 milliseconds
121065.38 requests per second====== RPOP ======100000 requests completed in 0.83 seconds100 parallel clients3 bytes payloadkeep alive: 199.87% <= 1 milliseconds
100.00% <= 1 milliseconds
120481.93 requests per second====== SADD ======100000 requests completed in 0.81 seconds100 parallel clients3 bytes payloadkeep alive: 199.93% <= 1 milliseconds
100.00% <= 1 milliseconds
123001.23 requests per second====== HSET ======100000 requests completed in 0.82 seconds100 parallel clients3 bytes payloadkeep alive: 199.85% <= 1 milliseconds
99.96% <= 5 milliseconds
100.00% <= 5 milliseconds
121951.22 requests per second====== SPOP ======100000 requests completed in 0.82 seconds100 parallel clients3 bytes payloadkeep alive: 199.89% <= 1 milliseconds
100.00% <= 1 milliseconds
121506.68 requests per second====== LPUSH (needed to benchmark LRANGE) ======100000 requests completed in 0.81 seconds100 parallel clients3 bytes payloadkeep alive: 199.68% <= 1 milliseconds
99.93% <= 3 milliseconds
100.00% <= 3 milliseconds
122850.12 requests per second====== LRANGE_100 (first 100 elements) ======100000 requests completed in 0.81 seconds100 parallel clients3 bytes payloadkeep alive: 199.78% <= 1 milliseconds
100.00% <= 1 milliseconds
123152.71 requests per second====== LRANGE_300 (first 300 elements) ======100000 requests completed in 0.81 seconds100 parallel clients3 bytes payloadkeep alive: 199.86% <= 1 milliseconds
100.00% <= 1 milliseconds
123456.79 requests per second====== LRANGE_500 (first 450 elements) ======100000 requests completed in 0.81 seconds100 parallel clients3 bytes payloadkeep alive: 199.87% <= 1 milliseconds
99.98% <= 2 milliseconds
100.00% <= 3 milliseconds
100.00% <= 3 milliseconds
123152.71 requests per second====== LRANGE_600 (first 600 elements) ======100000 requests completed in 0.81 seconds100 parallel clients3 bytes payloadkeep alive: 199.90% <= 1 milliseconds
100.00% <= 1 milliseconds
122850.12 requests per second====== MSET (10 keys) ======100000 requests completed in 0.73 seconds100 parallel clients3 bytes payloadkeep alive: 199.28% <= 1 milliseconds
99.87% <= 2 milliseconds
99.88% <= 9 milliseconds
99.89% <= 10 milliseconds
99.98% <= 20 milliseconds
100.00% <= 20 milliseconds
136239.78 requests per second

Redis-benchmark测试Redis性能相关推荐

YCSB benchmark测试mongodb性能——和web服务器测试性能结果类似
转自:http://blog.sina.com.cn/s/blog_48c95a190102v9kg.html YCSB(Yahoo! Cloud Serving Benchmark) ...
YCSB benchmark测试cassandra性能——和web服务器测试性能结果类似
转自:http://www.itdadao.com/articles/c15a531189p0.html http://www.cnblogs.com/bettersky/p/6158172.html ...
Redis 压力测试服务监控
Redis 压力测试 & 服务监控 Redis 压力测试 Redis 安装成功后,会在 /usr/local/bin/目录下生成redis-benchmark压测工具.该工具模拟N个客户端同时 ...
redis 缓存测试
redis 缓存测试 redis 缓存测试 redis介绍 redis测试点 redis查看工具 redis常用命令 redis 缓存测试 redis介绍地址:https://redis.io/ r ...
linux下清理redis缓存文件夹,redis的安装和清理缓存操作
Redis的脚本安装参考文章: 第一步编译redis 第二步拷贝redis执行文件,修改配置文件,并启动批量关闭redis端口 8001到8009 批量启动redis端口 8001到8009 ...
redis和mysql内存数据库性能_Redis高性能内存数据库
(一)什么是Redis? Redis是一个key-value存储系统.和Memcached类似,它支持存储的value类型相对更多,包括string(字符串).list(链表).set(集合).zse ...
由浅入深解读Redis高级能力及性能调优
摘要本文将从Redis的基本特性入手,通过讲述Redis的数据结构和主要命令对Redis的基本能力进行直观介绍.之后概览Redis提供的高级能力,并在部署.维护.性能调优等多个方面进行更深入的介绍和 ...
如何检查python的库是否安装成功_如何测试redis是否安装成功
下载Redis 下载好后复制所在位置 cd 跳到 D:\Java\64bit 图中的目录位置这样便启动成功了. 设置redis密码的话要到redis.conf中找到 requirepass关键字 ...
上手测试GaussDB(for Redis) 和开源 Redis，只为推荐质优价廉的Redis
本文分享自华为云社区<程序员硬核测评:全方位测评 GaussDB(for Redis) 和开源 Redis>,作者:高斯Redis官方博客. 正值企业数字化转型全面提速之际,业务需求急速增 ...

Redis-benchmark测试Redis性能

Redis-benchmark是官方自带的Redis性能测试工具，可以有效的测试Redis服务的性能。

Redis-benchmark测试Redis性能相关推荐

最新文章

热门文章