服务器之家:专注于服务器技术及软件下载分享
分类导航

Mysql|Sql Server|Oracle|Redis|MongoDB|PostgreSQL|Sqlite|DB2|mariadb|Access|数据库技术|

服务器之家 - 数据库 - Redis - 关于redis状态监控和性能调优详解

关于redis状态监控和性能调优详解

2019-11-08 14:54天生帅才 Redis

Redis是一种高级key-value数据库。它跟memcached类似,不过数据可以持久化,而且支持的数据类型很丰富。有字符串,链表、哈希、集合和有序集合5种。下面这篇文章主要给大家介绍了关于redis状态监控和性能调优的相关资料,需要的朋

前言

对于任何应用服务和组件,都需要一套完善可靠谱监控方案。

尤其redis这类敏感的纯内存、高并发和低延时的服务,一套完善的监控告警方案,是精细化运营的前提。

本文主要给大家介绍了关于redis状态监控和性能调优的相关内容,分享出来供大家参考学习,下面话不多说了,来一起看看详细的介绍吧。

1、redis-benchmark

redis基准信息,redis服务器性能检测

例如:

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

?
1
redis-benchmark -h localhost -p 6379 -c 100 -n 100000
?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
[root@redis-server ~]# redis-benchmark -h localhost -p 6379 -c 100 -n 100000
====== PING_INLINE ======
requests completed in 1.29 seconds
parallel clients
bytes payload
 keep alive: 1
 
81.97% <= 1 milliseconds
97.69% <= 2 milliseconds
99.79% <= 3 milliseconds
99.94% <= 4 milliseconds
99.97% <= 5 milliseconds
100.00% <= 5 milliseconds
77639.75 requests per second
 
====== PING_BULK ======
requests completed in 1.49 seconds
parallel clients
bytes payload
 keep alive: 1
 
73.04% <= 1 milliseconds
97.46% <= 2 milliseconds
99.62% <= 3 milliseconds
99.97% <= 4 milliseconds
100.00% <= 5 milliseconds
100.00% <= 5 milliseconds
67204.30 requests per second
 
====== SET ======
requests completed in 1.30 seconds
parallel clients
bytes payload
 keep alive: 1
 
81.09% <= 1 milliseconds
97.16% <= 2 milliseconds
99.43% <= 3 milliseconds
99.75% <= 4 milliseconds
99.80% <= 5 milliseconds
99.82% <= 7 milliseconds
99.83% <= 8 milliseconds
99.85% <= 9 milliseconds
99.87% <= 10 milliseconds
99.89% <= 11 milliseconds
99.89% <= 12 milliseconds
99.90% <= 13 milliseconds
99.90% <= 14 milliseconds
99.90% <= 15 milliseconds
99.91% <= 16 milliseconds
99.93% <= 17 milliseconds
99.94% <= 18 milliseconds
99.95% <= 19 milliseconds
99.96% <= 20 milliseconds
99.98% <= 21 milliseconds
99.99% <= 22 milliseconds
100.00% <= 23 milliseconds
100.00% <= 23 milliseconds
76687.12 requests per second
 
====== GET ======
requests completed in 1.91 seconds
parallel clients
bytes payload
 keep alive: 1
 
49.74% <= 1 milliseconds
93.92% <= 2 milliseconds
99.37% <= 3 milliseconds
99.95% <= 4 milliseconds
99.97% <= 5 milliseconds
99.98% <= 6 milliseconds
100.00% <= 6 milliseconds
52273.91 requests per second
 
====== INCR ======
requests completed in 1.60 seconds
parallel clients
bytes payload
 keep alive: 1
 
66.32% <= 1 milliseconds
96.55% <= 2 milliseconds
99.61% <= 3 milliseconds
99.96% <= 4 milliseconds
100.00% <= 5 milliseconds
62344.14 requests per second
 
====== LPUSH ======
requests completed in 1.27 seconds
parallel clients
bytes payload
 keep alive: 1
 
73.84% <= 1 milliseconds
95.61% <= 2 milliseconds
99.36% <= 3 milliseconds
99.96% <= 4 milliseconds
99.99% <= 5 milliseconds
100.00% <= 5 milliseconds
78492.93 requests per second
 
====== RPUSH ======
requests completed in 1.31 seconds
parallel clients
bytes payload
 keep alive: 1
 
80.47% <= 1 milliseconds
96.93% <= 2 milliseconds
99.56% <= 3 milliseconds
99.98% <= 4 milliseconds
100.00% <= 5 milliseconds
100.00% <= 5 milliseconds
76103.50 requests per second
 
====== LPOP ======
requests completed in 1.30 seconds
parallel clients
bytes payload
 keep alive: 1
 
74.91% <= 1 milliseconds
95.50% <= 2 milliseconds
99.29% <= 3 milliseconds
99.95% <= 4 milliseconds
100.00% <= 5 milliseconds
100.00% <= 5 milliseconds
77101.00 requests per second
 
====== RPOP ======
requests completed in 1.40 seconds
parallel clients
bytes payload
 keep alive: 1
 
77.99% <= 1 milliseconds
97.07% <= 2 milliseconds
99.61% <= 3 milliseconds
99.97% <= 4 milliseconds
99.98% <= 5 milliseconds
100.00% <= 6 milliseconds
100.00% <= 6 milliseconds
71377.59 requests per second
 
====== SADD ======
requests completed in 1.32 seconds
parallel clients
bytes payload
 keep alive: 1
 
80.83% <= 1 milliseconds
97.14% <= 2 milliseconds
99.57% <= 3 milliseconds
99.95% <= 4 milliseconds
100.00% <= 5 milliseconds
100.00% <= 5 milliseconds
75757.57 requests per second
 
====== HSET ======
requests completed in 1.30 seconds
parallel clients
bytes payload
 keep alive: 1
 
80.25% <= 1 milliseconds
96.83% <= 2 milliseconds
99.49% <= 3 milliseconds
99.97% <= 4 milliseconds
100.00% <= 4 milliseconds
76923.08 requests per second
 
====== SPOP ======
requests completed in 1.48 seconds
parallel clients
bytes payload
 keep alive: 1
 
73.97% <= 1 milliseconds
96.91% <= 2 milliseconds
99.55% <= 3 milliseconds
99.96% <= 4 milliseconds
100.00% <= 5 milliseconds
100.00% <= 5 milliseconds
67567.57 requests per second
 
====== LPUSH (needed to benchmark LRANGE) ======
requests completed in 1.35 seconds
parallel clients
bytes payload
 keep alive: 1
 
71.03% <= 1 milliseconds
95.36% <= 2 milliseconds
99.29% <= 3 milliseconds
99.97% <= 4 milliseconds
100.00% <= 5 milliseconds
100.00% <= 5 milliseconds
73909.83 requests per second
 
====== LRANGE_100 (first 100 elements) ======
requests completed in 2.91 seconds
parallel clients
bytes payload
 keep alive: 1
 
14.30% <= 1 milliseconds
80.30% <= 2 milliseconds
94.42% <= 3 milliseconds
96.88% <= 4 milliseconds
98.34% <= 5 milliseconds
99.39% <= 6 milliseconds
99.78% <= 7 milliseconds
99.93% <= 8 milliseconds
99.97% <= 9 milliseconds
99.98% <= 10 milliseconds
100.00% <= 11 milliseconds
100.00% <= 11 milliseconds
34317.09 requests per second
 
====== LRANGE_300 (first 300 elements) ======
requests completed in 5.88 seconds
parallel clients
bytes payload
 keep alive: 1
 
0.00% <= 2 milliseconds
85.83% <= 3 milliseconds
94.17% <= 4 milliseconds
96.10% <= 5 milliseconds
97.90% <= 6 milliseconds
98.68% <= 7 milliseconds
98.70% <= 8 milliseconds
99.30% <= 9 milliseconds
99.49% <= 10 milliseconds
99.76% <= 11 milliseconds
99.79% <= 12 milliseconds
99.83% <= 13 milliseconds
99.85% <= 14 milliseconds
99.87% <= 15 milliseconds
99.89% <= 16 milliseconds
99.91% <= 17 milliseconds
99.92% <= 19 milliseconds
99.93% <= 20 milliseconds
99.94% <= 21 milliseconds
99.95% <= 22 milliseconds
99.96% <= 23 milliseconds
99.97% <= 24 milliseconds
99.99% <= 25 milliseconds
99.99% <= 26 milliseconds
100.00% <= 27 milliseconds
17006.80 requests per second
 
====== LRANGE_500 (first 450 elements) ======
requests completed in 8.16 seconds
parallel clients
bytes payload
 keep alive: 1
 
0.00% <= 2 milliseconds
0.01% <= 3 milliseconds
80.98% <= 4 milliseconds
90.89% <= 5 milliseconds
95.60% <= 6 milliseconds
97.20% <= 7 milliseconds
98.23% <= 8 milliseconds
98.53% <= 9 milliseconds
99.06% <= 10 milliseconds
99.09% <= 11 milliseconds
99.46% <= 12 milliseconds
99.53% <= 13 milliseconds
99.65% <= 14 milliseconds
99.75% <= 15 milliseconds
99.79% <= 16 milliseconds
99.81% <= 17 milliseconds
99.82% <= 18 milliseconds
99.84% <= 19 milliseconds
99.85% <= 20 milliseconds
99.86% <= 21 milliseconds
99.87% <= 22 milliseconds
99.88% <= 23 milliseconds
99.89% <= 24 milliseconds
99.90% <= 25 milliseconds
99.91% <= 26 milliseconds
99.93% <= 27 milliseconds
99.93% <= 28 milliseconds
99.94% <= 29 milliseconds
99.95% <= 30 milliseconds
99.96% <= 31 milliseconds
99.98% <= 32 milliseconds
99.98% <= 33 milliseconds
99.99% <= 34 milliseconds
99.99% <= 35 milliseconds
100.00% <= 36 milliseconds
100.00% <= 36 milliseconds
12260.91 requests per second
 
====== LRANGE_600 (first 600 elements) ======
requests completed in 10.15 seconds
parallel clients
bytes payload
 keep alive: 1
 
0.00% <= 3 milliseconds
0.01% <= 4 milliseconds
84.84% <= 5 milliseconds
93.41% <= 6 milliseconds
96.43% <= 7 milliseconds
97.71% <= 8 milliseconds
97.75% <= 9 milliseconds
98.32% <= 10 milliseconds
98.79% <= 11 milliseconds
99.19% <= 12 milliseconds
99.22% <= 13 milliseconds
99.25% <= 14 milliseconds
99.48% <= 15 milliseconds
99.56% <= 16 milliseconds
99.60% <= 17 milliseconds
99.68% <= 18 milliseconds
99.74% <= 19 milliseconds
99.77% <= 20 milliseconds
99.79% <= 21 milliseconds
99.82% <= 22 milliseconds
99.83% <= 23 milliseconds
99.85% <= 24 milliseconds
99.86% <= 25 milliseconds
99.86% <= 26 milliseconds
99.87% <= 27 milliseconds
99.88% <= 28 milliseconds
99.89% <= 29 milliseconds
99.90% <= 30 milliseconds
99.90% <= 31 milliseconds
99.91% <= 32 milliseconds
99.91% <= 33 milliseconds
99.92% <= 34 milliseconds
99.94% <= 35 milliseconds
99.95% <= 36 milliseconds
99.95% <= 37 milliseconds
99.96% <= 38 milliseconds
99.96% <= 39 milliseconds
99.96% <= 40 milliseconds
99.97% <= 41 milliseconds
99.98% <= 42 milliseconds
99.98% <= 43 milliseconds
99.99% <= 44 milliseconds
99.99% <= 45 milliseconds
99.99% <= 46 milliseconds
100.00% <= 47 milliseconds
100.00% <= 47 milliseconds
9851.25 requests per second
 
====== MSET (10 keys) ======
requests completed in 1.89 seconds
parallel clients
bytes payload
 keep alive: 1
 
0.00% <= 1 milliseconds
75.00% <= 2 milliseconds
89.85% <= 3 milliseconds
95.38% <= 4 milliseconds
98.52% <= 5 milliseconds
99.34% <= 6 milliseconds
99.60% <= 7 milliseconds
99.83% <= 8 milliseconds
99.98% <= 9 milliseconds
100.00% <= 9 milliseconds
52994.17 requests per second
 
 
[root@redis-server ~]#

2、redis-cli

例1:监控本机6379端口的实例的数据操作,redis的连接及读写操作

?
1
redis-cli -h localhost -p 6379 monitor

先开启一个终端1,用于redis监控

?
1
2
3
4
5
[root@redis-server ~]# redis-cli -h localhost -p 6379 monitor
OK
1504689350.635365 [0 127.0.0.1:57996] "COMMAND"
1504689361.944610 [0 127.0.0.1:57996] "set" "a" "1"
1504689369.782029 [0 127.0.0.1:57996] "get" "a"

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

?
1
2
3
4
5
6
[root@redis-server ~]# redis-cli -p 6379
127.0.0.1:6380> set a 1
OK
127.0.0.1:6380> get a
"1"
127.0.0.1:6380>

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

例2:查询本机redis实例的信息,端口6379

?
1
redis-cli -h localhost -p 6379 info

备注:该命令也可以在redis终端里面进行查询

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
[root@redis-server ~]# redis-cli -h localhost -p 6379 info
# Server
redis_version:3.2.10
redis_git_sha1:00000000
redis_git_dirty:0
redis_build_id:eae5a0b8746eb6ce
redis_mode:standalone
os:Linux 2.6.32-431.el6.x86_64 x86_64
arch_bits:64
multiplexing_api:epoll
gcc_version:4.4.7
process_id:6003
run_id:0057d03b2e908ee036c2aa1c3531e8aa051d7468
tcp_port:6379
uptime_in_seconds:159221
uptime_in_days:1
hz:10
lru_clock:11517636
executable:/usr/local/redis/bin/redis-server
config_file:/usr/local/redis/conf/redis.conf
 
# Clients
connected_clients:1
client_longest_output_list:0
client_biggest_input_buf:0
blocked_clients:0
 
# Memory
used_memory:1828104
used_memory_human:1.74M
used_memory_rss:4050944
used_memory_rss_human:3.86M
used_memory_peak:8439360
used_memory_peak_human:8.05M
total_system_memory:1960443904
total_system_memory_human:1.83G
used_memory_lua:37888
used_memory_lua_human:37.00K
maxmemory:0
maxmemory_human:0B
maxmemory_policy:noeviction
mem_fragmentation_ratio:2.22
mem_allocator:jemalloc-4.0.3
 
# Persistence
loading:0
rdb_changes_since_last_save:0
rdb_bgsave_in_progress:0
rdb_last_save_time:1504689256
rdb_last_bgsave_status:ok
rdb_last_bgsave_time_sec:0
rdb_current_bgsave_time_sec:-1
aof_enabled:0
aof_rewrite_in_progress:0
aof_rewrite_scheduled:0
aof_last_rewrite_time_sec:-1
aof_current_rewrite_time_sec:-1
aof_last_bgrewrite_status:ok
aof_last_write_status:ok
 
# Stats
total_connections_received:3603
total_commands_processed:3600007
instantaneous_ops_per_sec:0
total_net_input_bytes:192800186
total_net_output_bytes:2634476722
instantaneous_input_kbps:0.00
instantaneous_output_kbps:0.00
rejected_connections:0
sync_full:0
sync_partial_ok:0
sync_partial_err:0
expired_keys:0
evicted_keys:0
keyspace_hits:1000003
keyspace_misses:0
pubsub_channels:0
pubsub_patterns:0
latest_fork_usec:408
migrate_cached_sockets:0
 
# Replication
role:master
connected_slaves:0
master_repl_offset:0
repl_backlog_active:0
repl_backlog_size:1048576
repl_backlog_first_byte_offset:0
repl_backlog_histlen:0
 
# CPU
used_cpu_sys:99.45
used_cpu_user:108.88
used_cpu_sys_children:0.01
used_cpu_user_children:0.01
 
# Cluster
cluster_enabled:0
 
# Keyspace
db0:keys=7,expires=0,avg_ttl=0
[root@redis-server ~]#

总结

以上就是这篇文章的全部内容了,希望本文的内容对大家的学习或者工作能带来一定的帮助,如果有疑问大家可以留言交流,谢谢大家对服务器之家的支持。

延伸 · 阅读

精彩推荐
  • RedisRedis分布式锁升级版RedLock及SpringBoot实现方法

    Redis分布式锁升级版RedLock及SpringBoot实现方法

    这篇文章主要介绍了Redis分布式锁升级版RedLock及SpringBoot实现,本文给大家介绍的非常详细,对大家的学习或工作具有一定的参考借鉴价值,需要的朋友可以...

    等不到的口琴7802021-07-25
  • Redisredis启动,停止,及端口占用处理方法

    redis启动,停止,及端口占用处理方法

    今天小编就为大家分享一篇redis启动,停止,及端口占用处理方法,具有很好的参考价值,希望对大家有所帮助。一起跟随小编过来看看吧 ...

    澄海单挑狂5152019-11-14
  • RedisRedis存取序列化与反序列化性能问题详解

    Redis存取序列化与反序列化性能问题详解

    这篇文章主要给大家介绍了关于Redis存取序列化与反序列化性能问题的相关资料,文中通过示例代码介绍的非常详细,对大家的学习或者工作具有一定的参...

    这名字已经存在9742021-02-24
  • Redis就这?Redis持久化策略——AOF

    就这?Redis持久化策略——AOF

    今天为大家介绍Redis的另一种持久化策略——AOF。注意:AOF文件只会记录Redis的写操作命令,因为读命令对数据的恢复没有任何意义...

    头发茂密的刘叔4052021-12-14
  • RedisRedis数据结构之链表与字典的使用

    Redis数据结构之链表与字典的使用

    这篇文章主要介绍了Redis数据结构之链表与字典的使用,文中通过示例代码介绍的非常详细,对大家的学习或者工作具有一定的参考学习价值,需要的朋友...

    白泽来了4052021-08-03
  • RedisLinux Redis 的安装步骤详解

    Linux Redis 的安装步骤详解

    这篇文章主要介绍了 Linux Redis 的安装步骤详解的相关资料,希望大家通过本文能掌握如何安装Redis,需要的朋友可以参考下 ...

    carl-zhao3822019-11-08
  • Redis在ssm项目中使用redis缓存查询数据的方法

    在ssm项目中使用redis缓存查询数据的方法

    本文主要简单的使用Java代码进行redis缓存,即在查询的时候先在service层从redis缓存中获取数据。如果大家对在ssm项目中使用redis缓存查询数据的相关知识感...

    caychen8962019-11-12
  • Redis聊一聊Redis与MySQL双写一致性如何保证

    聊一聊Redis与MySQL双写一致性如何保证

    一致性就是数据保持一致,在分布式系统中,可以理解为多个节点中数据的值是一致的。本文给大家分享Redis与MySQL双写一致性该如何保证,感兴趣的朋友一...

    mind_programmonkey6432021-08-12