redis中状态监控与性​​能调优实例分析

1. redis-benchmark

redis基准信息，redis服务器性能测试

例如：

检测redis服务器性能，端口6379的本地实例，100个并发连接，100000个请求

redis-benchmark -h localhost -p 6379 -c 100 -n 100000

[root@redis-server ~]# redis-benchmark -h localhost -p 6379 -c 100 -n 100000 ==== == PING_INLINE ======请求在 1.29 秒内完成并行客户端字节负载保持活动状态：181.97% <= 1 毫秒97.69% <= 2 毫秒99.79% <= 3 毫秒99.94% <= 4 毫秒99.97% <= 5毫秒100.00% <= 5 毫秒77639.75 每秒请求====== PING_BULK ======请求在 1.49 秒内完成并行客户端字节负载保持活动状态：173.04% <= 1 毫秒97.46% <= 2 毫秒99. 62% <= 3 毫秒99.97% <= 4 毫秒100.00% <= 5 毫秒100.00% <= 5 毫秒67204.30 每秒请求====== SET ======请求在 1.30 秒内完成并行客户端字节负载保持活动状态：181.09% <= 1 毫秒97.16% <= 2 毫秒99.43% <= 3 毫秒99.75% <= 4 毫秒99.80% <= 5 毫秒99.82% <= 7 毫秒99.83% <= 8 毫秒99.85% <= 9 毫秒99.87% <= 10 毫秒99 .89% <= 11 毫秒99.89% <= 12 毫秒99.90% <= 13 毫秒99.90% <= 14 毫秒99.90% < = 15毫秒99.91% <= 16毫秒99.93% <= 17毫秒99.94% <= 18毫秒99.95% <= 19毫秒99.96% <= 20毫秒99.98% <= 21毫秒99.99% <= 22 毫秒100.00% <= 23 毫秒100.00% <=每秒 23 毫秒76687.12 个请求= ===== GET ======在 1.91 秒内完成的请求并行客户端字节负载保持活动状态：149.74% <= 1 毫秒93.92% <= 2 毫秒99.37% <= 3毫秒99.95% <= 4 毫秒99. 97% <= 5 毫秒99.98% <= 6 毫秒100.00% <= 6 毫秒52273.91 每秒请求====== INCR ======请求在 1.60 秒内完成并行客户端字节有效负载保持活动：166.32 % <= 1 毫秒96.55% <= 2 毫秒99.61% <= 3 毫秒99.96% <= 4 毫秒100.00% <= 5 毫秒62344.14 每秒请求====== LPUSH ===== =在 1.27 秒内完成的请求并行客户端字节负载保持活动状态：173.84% <= 1 毫秒95.61% <= 2 毫秒99.36% <= 3 毫秒99.96% <= 4 毫秒99.99% <= 5 毫秒100.00% <=每秒 5 毫秒78492.93 个请求=== === RPUSH ======请求在 1.31 秒内完成并行客户端字节负载保持活动状态：180.47% <= 1 毫秒96.93% <= 2 milliseconds99.56% <= 3 毫秒99.98% <= 4 毫秒100.00% <= 5 毫秒100.00% <= 5 毫秒76103.50 每秒请求====== LPOP ======请求完成时间1.30 秒并行客户端字节有效负载保持活动状态：174.91% <= 1 毫秒95.50% <= 2 毫秒99.29% <= 3 毫秒99。 95% <= 4 毫秒100.00% <= 5 毫秒100.00% <= 5 毫秒77101.00 每秒请求====== RPOP ======请求在 1.40 秒内完成并行客户端字节负载保持活动状态：177.99% <= 1 毫秒97.07%<= 2 MilliseConds99.61%<= 3 MilliseConds99.97%<= 4 毫秒 99.98%<= 5 毫秒100.00%<= 6 毫秒100.00%<= 6 MilliseConds71377 .59 个请求第二====== SADD ======请求在1.32秒内完成并行客户端字节有效负载保持活动：180.83% <= 1毫秒97.14% <= 2毫秒99.57% <= 3毫秒99.95 % <= 4 milliseconds100.00% <= 5 milliseconds100.00% <= 5 milliseconds75757.57 每秒请求数====== HSET ======requests com在 1.30 秒内完成并行客户端字节负载保持活动状态：180.25% <= 1 毫秒96.83% <= 2 毫秒99.49% <= 3 毫秒99.97% <= 4 毫秒100.00% <= 4 毫秒76923.08 每秒请求= ===== SPOP ======请求在 1.48 秒内完成并行客户端字节有效负载保持活动：173.97%<= 1 MilliseConds96.91%<= 2 Milliseconds99.55%<= 3 MilliseConds99.96%<= 4 Millises100。 00%<= 5 毫秒100.00%< = 5 MilliseConds67567.57 每秒请求数 =====LPUSH（需要对 LRANGE 进行基准测试）======请求在 1.35 秒内完成并行客户端字节负载保持活动状态：171.03% < = 1 毫秒95.36% <= 2 毫秒99.29% <= 3 毫秒99.97 % <= 4 millISECONDS100.00%<= 5 MilliseConds100.00%<= 5 毫秒73909.83 每秒请求数 ======= LRANGE_100（前 100 个元素）================================================ =================================================== =================================================== ======================================================,, 2. 91 SecondSparallel ClientsBytes 有效负载保持活动状态: 114.30% <= 1 毫秒80.30% <= 2 毫秒94.42% <= 3毫秒96.88% <= 4毫秒98.34% <= 5毫秒99.39% <= 6毫秒99.78% <= 7毫秒99.93% <= 8毫秒99.97% <= 9毫秒99.98% < = 10 毫秒100.00% <= 11 毫秒100.00% <= 11 毫秒34317.09 每秒请求数====== LRANGE_300（前 300 个元素）======请求在 5.88 秒内完成并行客户端字节负载保持活动状态： 10.00% <= 2 毫秒85.83% <= 3 毫秒94.17% <= 4 毫秒96.10% <= 5 毫秒97.90% <= 6 毫秒98.68% <= 7 毫秒98. 70% <= 8 毫秒99.30% <= 9 毫秒99.49% <= 10 毫秒99.76% <= 11 毫秒99.79% <= 12 毫秒99.83% <= 13 毫秒99.85% <= 14 毫秒99.87 % <= 15 毫秒99.89% <= 16 毫秒99.91% <= 17 毫秒99.92% <= 19 毫秒99.93% <= 20 毫秒99.94% <= 21 毫秒99.95% <= 22 毫秒99.96% <= 23 毫秒99.97% <= 24 毫秒99.99% <= 25 毫秒99.99% <= 26 毫秒100.00% <= 27 毫秒17006.80 每秒请求数===== = LRANGE_500（前 450 个元素）======请求在 8.16 秒内完成并行字节有效负载保持活动状态：10.00% <= 2 毫秒0.01% <= 3 毫秒80.98% <= 4 毫秒90.89% <= 5 毫秒95 .60% <= 6 毫秒97.20% <= 7 毫秒98.23% 客户端 <= 8 毫秒98.53% <= 9 毫秒99.06% <= 10 毫秒99.09% <= 11 毫秒99.46% <= 12 毫秒99 .53% <= 13 毫秒99.65% <= 14 毫秒99.75% <= 15 毫秒99.79% <= 16 毫秒99.81% <= 17 毫秒99.82% <= 18 毫秒99.84% <= 19 毫秒99. 85% <= 20 毫秒99.86% <= 21 毫秒99.87% <= 22 毫秒99.88% <= 23 毫秒99 .89% <= 24 毫秒99.90% <= 25 毫秒99.91% <= 26 毫秒99. 93% <= 27 毫秒99.93% <= 28 毫秒99.94% <= 29 毫秒99.95% <=30 毫秒99. 96% <= 31 毫秒99.98% <= 32 毫秒99.98% <= 33 毫秒99.99% <= 34 毫秒99.99% <= 35 毫秒100.00% <= 36 毫秒100.00% <= 36 毫秒122 60.91 个请求每秒====== LRANGE_600（前 600 个元素）======请求在 10.15 秒内完成并行客户端字节负载保持活动状态：10.00% <= 3 毫秒0.01% <= 4 毫秒84.84% <= 5 毫秒93 .41% <= 6 毫秒96.43% <= 7 毫秒97.71% <= 8 毫秒97.75% <= 9 毫秒98.32% <= 10 毫秒98.79% <= 11 毫秒99.19% <= 12 毫秒99. 22% <= 13 毫秒99.25% <= 14 毫秒99.48%<= 15 MilliseConds99.56%<= 16 MilliseConds99.60%<= 17 MilliseConds99.68%<= 18 MilliseConds99.74%<= 19 毫秒999999 .77 %<= 20 MilliseConds99.79%<= 21 毫秒99.82% <= 22 毫秒99.83% <= 23 毫秒99.85% <= 24 毫秒99.86% <= 25 毫秒99.86% <= 26 毫秒99.87% <= 27 毫秒99.88% <= 28 毫秒99.89% <= 29 英里毫秒 99 .90% <= 30 毫秒99.90% <= 31 毫秒99.91% <= 32 毫秒99.91% <= 33 毫秒99.92% <= 34 毫秒99.94% <= 35 毫秒99.95% <= 36毫秒99。 95%<= 37 MilliseConds99.96%<= 38 MilliseConds99.96%<= 39 MilliseConds 99.96%<= 40 毫秒 99.97%<= 41 毫秒 <= 42 毫秒99.98%<= 43 MilliseConds99.99 % <= 44毫秒99.99% <= 45 毫秒99.99% <= 46 毫秒100.00% <= 47 毫秒100.00% <= 47 毫秒9851.25 每秒请求====== MSET (10 个键) ===== =在 1.89 秒内完成的请求并行客户端字节负载保持活动状态：10.00% <= 1 毫秒75.00% <= 2 毫秒89.85% <= 3 毫秒95.38% <= 4 毫秒98.52% <= 5 毫秒99.34% <= 6 毫秒99.60% <= 7 毫秒99 .83% <= 8 毫秒99.98% <= 9 毫秒100.00% <= 9 毫秒52994.17 每秒请求数[root@redis-server ~]#

<强>2. redis-cli

示例1：监控数据操作本机6379端口上实例的ons、redis连接及读写操作

redis-cli -h localhost -p 6379monitor

首先打开一个终端1进行redis监控

[root@redis-server ~]# redis-cli -h localhost -p 6379 monitor OK1504689350.635365 [ 0 127.0.0.1:57996]“命令”1504689361.944610 [0 127.0.0.1:57996]“设置”“a”“1”1504689369.782029 [0 127.0.0.1:57996]“获取”“a”

然后打开一个redis终端2进行操作

[root@redis-server ~]# redis-cli -p 6379127.0.0.1:6380>设置一个1OK127.0.0.1 :6380> get a "1"127.0.0.1:6380>

可以看到终端2上进行的数据操作都会记录在终端1上

示例2 ：查询本地redis实例信息，端口6379

redis-cli -h localhost -p 6379 info
注意：该命令也可以在redis终端中查询
[root@redis-server ~]# redis-cli -h localhost -p 6379 info # Serverredis_version:3.2.10redis_git_sha1:00000000redis_git_dirty:0redis_build_id:eae5a0b8746eb6ceredis_mode:standaloneos:Linux 2.6.32-431.el6 .x86_64 x86_64arch_bits：64多路复用_api：epollg cc_version：4.4.7process_id：6003run_id：0057d03b2e908ee036c2aa1c3531e8aa051d7468tcp_port：6379uptime_in_秒：159221uptime_in_days：1 hz:10lru_clock:11517636可执行文件: /usr/local/redis/bin/redis-serverconfig_file:/usr/local/redis/conf/redis .conf# Clientsconnected_clients:1client_longest_output_list:0client_biggest_input_buf:0blocked_clients:0# Memoryused_memory:1828104used_memory_ human:1.74Mused_memory_rss:40 50944used_memory_rss_ human:3.86Mused_memory_peak:8439360used_memory_peak_ human:8.05Mto tal_system_memory：1960443904total_system_memory_ human：1.83Gused_memory_lua：37888used_memory_lua_ human：37.00Kmaxmemory：0maxmemory_ human：0Bmaxmemory_policy：noevictionmem_fragmentation_ratio：2.22mem_allocator： je malloc-4.0.3# 持久化加载：0rdb_changes_since_last_save：0rdb_bgsave_in_progress：0rdb_last_save_time：1504689256rdb_last_bgsave_status：okrdb_last_bgsave_time_sec：0rdb_current_bgsave_time_sec：-1aof_enabled：0aof_rewrite_in_progress：0aof_rewrite_scheduled： 0aof_last_rewrite_time_sec:-1aof_current _rewrite_time_sec:-1aof_last_bgrewrite_status:okaof_last_write_status:ok# Statstotal_connections_received:3603total_commands_processed:3600007instantaneous_ops_per_sec:0total_net_input_bytes:192800186总网络输出字节：26344767 22instantaneous_input_kbps：0.00instantaneous_output_kbps： 0.00rejected_connections：0sync_full：0sync_partial_ok：0sync_partial_err：0expired_keys：0evicted_keys：0keyspace_hits：1000003keyspace_misses：0pubsub_channels：0pubsub_patterns：0latest_fork_usec：408migrate_cached_sockets：0＃Replicationrole：masterconnected_从机：0master_repl_offset：0repl_backlog_active：0repl_backlog_size：1048576repl_backlog_first_byte_offset：0repl_backlog_histlen：0＃CPUused_cpu_sys：99.45used_cpu_user：108.88used_cpu_sys_children:0.01used_cpu_user_children:0.01# Clustercluster_enabled:0# Keyspacedb0:keys=7,expires=0,avg_ttl=0[root@redis-server ~]#
以上是《Redis》状态监控和本文《性能调优示例分析》的全部内容，感谢您的阅读！相信大家都有了一定的了解，希望分享的内容对大家有所帮助，如果您想了解更多知识请关注行业资讯频道！