使用Windows版Redis

1、下载Windows版本的Redis

2、在redis目录里创建redis.conf

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
# Redis configuration file example
 
# By default Redis does not run as a daemon. Use 'yes' if you need it.
# Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
# 说明:Windows does not support daemonize.
<strong>daemonize no</strong>
 
# When run as a daemon, Redis write a pid file in /var/run/redis.pid by default.
# You can specify a custom pid file location here.
pidfile /var/run/redis.pid
 
# Accept connections on the specified port, default is 6379
port 6379
 
# If you want you can bind a single interface, if the bind option is not
# specified all the interfaces will listen for connections.
#
# bind 127.0.0.1
 
# Close the connection after a client is idle for N seconds (0 to disable)
timeout 300
 
# Set server verbosity to 'debug'
# it can be one of:
# debug (a lot of information, useful for development/testing)
# notice (moderately verbose, what you want in production probably)
# warning (only very important / critical messages are logged)
loglevel debug
 
# Specify the log file name. Also 'stdout' can be used to force
# the demon to log on the standard output. Note that if you use standard
# output for logging but daemonize, logs will be sent to /dev/null
logfile stdout
 
# Set the number of databases. The default database is DB 0, you can select
# a different one on a per-connection basis using SELECT <dbid> where
# dbid is a number between 0 and 'databases'-1
databases 16
 
################################ SNAPSHOTTING #################################
#
# Save the DB on disk:
#
# save <seconds> <changes>
#
# Will save the DB if both the given number of seconds and the given
# number of write operations against the DB occurred.
#
# In the example below the behaviour will be to save:
# after 900 sec (15 min) if at least 1 key changed
# after 300 sec (5 min) if at least 10 keys changed
# after 60 sec if at least 10000 keys changed
save 900 1
save 300 10
save 60 10000
 
# Compress string objects using LZF when dump .rdb databases?
# For default that's set to 'yes' as it's almost always a win.
# If you want to save some CPU in the saving child set it to 'no' but
# the dataset will likely be bigger if you have compressible values or keys.
rdbcompression yes
 
# The filename where to dump the DB
dbfilename dump.rdb
 
# For default save/load DB in/from the working directory
# Note that you must specify a directory not a file name.
dir ./
 
################################# REPLICATION #################################
 
# Master-Slave replication. Use slaveof to make a Redis instance a copy of
# another Redis server. Note that the configuration is local to the slave
# so for example it is possible to configure the slave to save the DB with a
# different interval, or to listen to another port, and so on.
#
# slaveof <masterip> <masterport>
 
# If the master is password protected (using the "requirepass" configuration
# directive below) it is possible to tell the slave to authenticate before
# starting the replication synchronization process, otherwise the master will
# refuse the slave request.
#
# masterauth <master-password>
 
################################## SECURITY ###################################
 
# Require clients to issue AUTH <password> before processing any other
# commands. This might be useful in environments in which you do not trust
# others with access to the host running redis-server.
#
# This should stay commented out for backward compatibility and because most
# people do not need auth (e.g. they run their own servers).
#
# requirepass foobared
 
################################### LIMITS ####################################
 
# Set the max number of connected clients at the same time. By default there
# is no limit, and it's up to the number of file descriptors the Redis process
# is able to open. The special value '0' means no limts.
# Once the limit is reached Redis will close all the new connections sending
# an error 'max number of clients reached'.
#
# maxclients 128
 
# Don't use more memory than the specified amount of bytes.
# When the memory limit is reached Redis will try to remove keys with an
# EXPIRE set. It will try to start freeing keys that are going to expire
# in little time and preserve keys with a longer time to live.
# Redis will also try to remove objects from free lists if possible.
#
# If all this fails, Redis will start to reply with errors to commands
# that will use more memory, like SET, LPUSH, and so on, and will continue
# to reply to most read-only commands like GET.
#
# WARNING: maxmemory can be a good idea mainly if you want to use Redis as a
# 'state' server or cache, not as a real DB. When Redis is used as a real
# database the memory usage will grow over the weeks, it will be obvious if
# it is going to use too much memory in the long run, and you'll have the time
# to upgrade. With maxmemory after the limit is reached you'll start to get
# errors for write operations, and this may even lead to DB inconsistency.
#
# maxmemory <bytes>
 
############################## APPEND ONLY MODE ###############################
 
# By default Redis asynchronously dumps the dataset on disk. If you can live
# with the idea that the latest records will be lost if something like a crash
# happens this is the preferred way to run Redis. If instead you care a lot
# about your data and don't want to that a single record can get lost you should
# enable the append only mode: when this mode is enabled Redis will append
# every write operation received in the file appendonly.log. This file will
# be read on startup in order to rebuild the full dataset in memory.
#
# Note that you can have both the async dumps and the append only file if you
# like (you have to comment the "save" statements above to disable the dumps).
# Still if append only mode is enabled Redis will load the data from the
# log file at startup ignoring the dump.rdb file.
#
# The name of the append only file is "appendonly.log"
#
# IMPORTANT: Check the BGREWRITEAOF to check how to rewrite the append
# log file in background when it gets too big.
 
appendonly no
 
# The fsync() call tells the Operating System to actually write data on disk
# instead to wait for more data in the output buffer. Some OS will really flush
# data on disk, some other OS will just try to do it ASAP.
#
# Redis supports three different modes:
#
# no: don't fsync, just let the OS flush the data when it wants. Faster.
# always: fsync after every write to the append only log . Slow, Safest.
# everysec: fsync only if one second passed since the last fsync. Compromise.
#
# The default is "always" that's the safer of the options. It's up to you to
# understand if you can relax this to "everysec" that will fsync every second
# or to "no" that will let the operating system flush the output buffer when
# it want, for better performances (but if you can live with the idea of
# some data loss consider the default persistence mode that's snapshotting).
 
appendfsync always
# appendfsync everysec
# appendfsync no
 
############################### ADVANCED CONFIG ###############################
 
# Glue small output buffers together in order to send small replies in a
# single TCP packet. Uses a bit more CPU but most of the times it is a win
# in terms of number of queries per second. Use 'yes' if unsure.
# glueoutputbuf yes
 
# Use object sharing. Can save a lot of memory if you have many common
# string in your dataset, but performs lookups against the shared objects
# pool so it uses more CPU and can be a bit slower. Usually it's a good
# idea.
#
# When object sharing is enabled (shareobjects yes) you can use
# shareobjectspoolsize to control the size of the pool used in order to try
# object sharing. A bigger pool size will lead to better sharing capabilities.
# In general you want this value to be at least the double of the number of
# very common strings you have in your dataset.
#
# WARNING: object sharing is experimental, don't enable this feature
# in production before of Redis 1.0-stable. Still please try this feature in
# your development environment so that we can test it better.
# shareobjects no
# shareobjectspoolsize 1024</bytes></password></master-password></masterport></masterip></changes></seconds></dbid>

3、创建redis.bat

1
redis-server.exe redis.conf

4、进入命令行窗口

5、启动redis

6、不要关闭上面的窗口,另外打开一个命令行窗口

7、使用redis(1)set与get

(2)使用listlpush, rpush, lpop, rpop, lrange

lrange start end0 —— 列表第一个元素-1 —— 列表倒数第一个元素-2 —— 列表倒数第二个元素 8、查看所有键keys *可使用通配符*和?keys a*keys ?b*

9、删除key//删除当前数据库中的所有Key??flushdb??//删除所有数据库中的key??flushall?

10、性能测试redis-benchmark.exe:性能测试,用以模拟同时由N个客户端发送M个 SETs/GETs 查询 (类似于 Apache 的 ab 工具)。 ./redis-benchmark -n 100000 –c 50

1
2
3
4
5
6
7
8
9
10
11
12
====== SET ======
100007 requests completed in 0.88 seconds (100004 查询完成于 1.14 秒 )
50 parallel clients (50个并发客户端)
3 bytes payload (3字节有效载荷)
keep alive: 1 (保持1个连接)
58.50% <= 0 milliseconds(毫秒)
99.17% <= 1 milliseconds
99.58% <= 2 milliseconds
99.85% <= 3 milliseconds
99.90% <= 6 milliseconds
100.00% <= 9 milliseconds
114293.71 requests per second(每秒 114293.71 次查询)

Windows下测试并发客户端极限为60。 E:\redis2.6.12>redis-benchmark -n 100000 -c 50

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
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
====== PING_INLINE ======
  100000 requests completed in 2.76 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1
 
2.87% <= 1 milliseconds
65.85% <= 2 milliseconds
99.68% <= 3 milliseconds
99.81% <= 4 milliseconds
99.95% <= 5 milliseconds
99.97% <= 6 milliseconds
99.97% <= 7 milliseconds
99.98% <= 8 milliseconds
99.98% <= 12 milliseconds
99.98% <= 13 milliseconds
99.98% <= 14 milliseconds
99.98% <= 15 milliseconds
99.98% <= 16 milliseconds
99.98% <= 17 milliseconds
99.99% <= 18 milliseconds
99.99% <= 19 milliseconds
99.99% <= 21 milliseconds
99.99% <= 23 milliseconds
99.99% <= 24 milliseconds
99.99% <= 25 milliseconds
99.99% <= 26 milliseconds
99.99% <= 27 milliseconds
100.00% <= 28 milliseconds
100.00% <= 30 milliseconds
100.00% <= 31 milliseconds
36231.88 requests per second
 
====== PING_BULK ======
  100000 requests completed in 2.75 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1
 
2.49% <= 1 milliseconds
67.44% <= 2 milliseconds
99.30% <= 3 milliseconds
99.72% <= 4 milliseconds
99.96% <= 5 milliseconds
99.97% <= 6 milliseconds
99.97% <= 7 milliseconds
99.98% <= 8 milliseconds
99.98% <= 11 milliseconds
99.98% <= 12 milliseconds
99.98% <= 13 milliseconds
99.98% <= 14 milliseconds
99.99% <= 15 milliseconds
99.99% <= 16 milliseconds
99.99% <= 17 milliseconds
99.99% <= 18 milliseconds
99.99% <= 20 milliseconds
99.99% <= 21 milliseconds
99.99% <= 23 milliseconds
99.99% <= 24 milliseconds
99.99% <= 25 milliseconds
99.99% <= 26 milliseconds
100.00% <= 27 milliseconds
100.00% <= 29 milliseconds
100.00% <= 30 milliseconds
100.00% <= 31 milliseconds
100.00% <= 32 milliseconds
100.00% <= 33 milliseconds
36350.42 requests per second
 
====== SET ======
  100000 requests completed in 2.92 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1
 
2.14% <= 1 milliseconds
60.02% <= 2 milliseconds
98.83% <= 3 milliseconds
99.67% <= 4 milliseconds
99.83% <= 5 milliseconds
99.91% <= 6 milliseconds
99.92% <= 7 milliseconds
99.92% <= 8 milliseconds
99.93% <= 9 milliseconds
99.94% <= 10 milliseconds
99.95% <= 11 milliseconds
99.96% <= 12 milliseconds
99.97% <= 13 milliseconds
99.98% <= 14 milliseconds
99.98% <= 15 milliseconds
99.98% <= 16 milliseconds
99.98% <= 17 milliseconds
99.98% <= 18 milliseconds
99.98% <= 19 milliseconds
99.99% <= 20 milliseconds
99.99% <= 21 milliseconds
99.99% <= 23 milliseconds
99.99% <= 24 milliseconds
99.99% <= 25 milliseconds
99.99% <= 26 milliseconds
99.99% <= 27 milliseconds
99.99% <= 28 milliseconds
99.99% <= 29 milliseconds
100.00% <= 30 milliseconds
100.00% <= 31 milliseconds
100.00% <= 33 milliseconds
100.00% <= 34 milliseconds
100.00% <= 35 milliseconds
100.00% <= 35 milliseconds
34211.43 requests per second
 
====== GET ======
  100000 requests completed in 2.80 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1
 
2.50% <= 1 milliseconds
64.56% <= 2 milliseconds
99.67% <= 3 milliseconds
99.87% <= 4 milliseconds
99.95% <= 5 milliseconds
99.95% <= 6 milliseconds
99.97% <= 7 milliseconds
99.97% <= 8 milliseconds
99.97% <= 10 milliseconds
99.97% <= 11 milliseconds
99.97% <= 12 milliseconds
99.98% <= 13 milliseconds
99.98% <= 14 milliseconds
99.98% <= 15 milliseconds
99.98% <= 18 milliseconds
99.98% <= 19 milliseconds
99.99% <= 20 milliseconds
99.99% <= 21 milliseconds
99.99% <= 22 milliseconds
99.99% <= 23 milliseconds
99.99% <= 24 milliseconds
99.99% <= 25 milliseconds
99.99% <= 26 milliseconds
99.99% <= 27 milliseconds
100.00% <= 28 milliseconds
100.00% <= 29 milliseconds
100.00% <= 30 milliseconds
100.00% <= 31 milliseconds
100.00% <= 33 milliseconds
100.00% <= 33 milliseconds
35752.59 requests per second
 
====== INCR ======
  100000 requests completed in 2.84 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1
 
2.61% <= 1 milliseconds
62.08% <= 2 milliseconds
99.53% <= 3 milliseconds
99.86% <= 4 milliseconds
99.96% <= 5 milliseconds
99.97% <= 6 milliseconds
99.97% <= 8 milliseconds
99.98% <= 9 milliseconds
99.98% <= 10 milliseconds
99.98% <= 11 milliseconds
99.98% <= 12 milliseconds
99.98% <= 13 milliseconds
99.98% <= 14 milliseconds
99.99% <= 15 milliseconds
99.99% <= 17 milliseconds
99.99% <= 18 milliseconds
99.99% <= 19 milliseconds
99.99% <= 20 milliseconds
99.99% <= 21 milliseconds
99.99% <= 22 milliseconds
99.99% <= 24 milliseconds
99.99% <= 25 milliseconds
100.00% <= 27 milliseconds
100.00% <= 28 milliseconds
100.00% <= 29 milliseconds
100.00% <= 30 milliseconds
100.00% <= 31 milliseconds
100.00% <= 31 milliseconds
35236.08 requests per second
 
====== LPUSH ======
  100000 requests completed in 2.88 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1
 
1.92% <= 1 milliseconds
60.62% <= 2 milliseconds
99.42% <= 3 milliseconds
99.91% <= 4 milliseconds
99.96% <= 5 milliseconds
99.97% <= 6 milliseconds
99.97% <= 7 milliseconds
99.97% <= 8 milliseconds
99.97% <= 9 milliseconds
99.97% <= 11 milliseconds
99.97% <= 12 milliseconds
99.97% <= 13 milliseconds
99.98% <= 14 milliseconds
99.98% <= 15 milliseconds
99.98% <= 16 milliseconds
99.98% <= 17 milliseconds
99.98% <= 18 milliseconds
99.98% <= 21 milliseconds
99.98% <= 22 milliseconds
99.99% <= 23 milliseconds
99.99% <= 24 milliseconds
99.99% <= 25 milliseconds
99.99% <= 26 milliseconds
99.99% <= 27 milliseconds
99.99% <= 28 milliseconds
99.99% <= 29 milliseconds
99.99% <= 30 milliseconds
99.99% <= 32 milliseconds
100.00% <= 34 milliseconds
100.00% <= 35 milliseconds
100.00% <= 36 milliseconds
100.00% <= 38 milliseconds
100.00% <= 38 milliseconds
34746.35 requests per second
 
====== LPOP ======
  100000 requests completed in 2.91 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1
 
2.31% <= 1 milliseconds
58.51% <= 2 milliseconds
99.40% <= 3 milliseconds
99.84% <= 4 milliseconds
99.96% <= 5 milliseconds
99.97% <= 6 milliseconds
99.97% <= 7 milliseconds
99.98% <= 8 milliseconds
99.98% <= 10 milliseconds
99.98% <= 12 milliseconds
99.98% <= 14 milliseconds
99.98% <= 15 milliseconds
99.98% <= 16 milliseconds
99.98% <= 19 milliseconds
99.99% <= 20 milliseconds
99.99% <= 21 milliseconds
99.99% <= 22 milliseconds
99.99% <= 23 milliseconds
99.99% <= 24 milliseconds
99.99% <= 25 milliseconds
99.99% <= 26 milliseconds
99.99% <= 27 milliseconds
99.99% <= 29 milliseconds
100.00% <= 31 milliseconds
100.00% <= 32 milliseconds
100.00% <= 33 milliseconds
100.00% <= 34 milliseconds
100.00% <= 35 milliseconds
100.00% <= 35 milliseconds
34305.32 requests per second
 
====== SADD ======
  100000 requests completed in 2.87 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1
 
1.80% <= 1 milliseconds
60.02% <= 2 milliseconds
99.65% <= 3 milliseconds
99.93% <= 4 milliseconds
99.96% <= 5 milliseconds
99.97% <= 6 milliseconds
99.97% <= 8 milliseconds
99.97% <= 10 milliseconds
99.97% <= 11 milliseconds
99.97% <= 12 milliseconds
99.97% <= 13 milliseconds
99.97% <= 14 milliseconds
99.98% <= 15 milliseconds
99.98% <= 16 milliseconds
99.98% <= 17 milliseconds
99.98% <= 18 milliseconds
99.98% <= 20 milliseconds
99.98% <= 21 milliseconds
99.98% <= 23 milliseconds
99.99% <= 25 milliseconds
99.99% <= 26 milliseconds
99.99% <= 27 milliseconds
99.99% <= 28 milliseconds
99.99% <= 30 milliseconds
99.99% <= 31 milliseconds
99.99% <= 32 milliseconds
99.99% <= 33 milliseconds
100.00% <= 34 milliseconds
100.00% <= 35 milliseconds
100.00% <= 36 milliseconds
100.00% <= 37 milliseconds
100.00% <= 38 milliseconds
34818.94 requests per second
 
====== SPOP ======
  100000 requests completed in 3.24 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1
 
2.13% <= 1 milliseconds
45.79% <= 2 milliseconds
98.24% <= 3 milliseconds
99.61% <= 4 milliseconds
99.86% <= 5 milliseconds
99.95% <= 6 milliseconds
99.98% <= 8 milliseconds
99.98% <= 9 milliseconds
99.98% <= 10 milliseconds
99.98% <= 12 milliseconds
99.98% <= 13 milliseconds
99.98% <= 15 milliseconds
99.98% <= 16 milliseconds
99.99% <= 17 milliseconds
99.99% <= 18 milliseconds
99.99% <= 19 milliseconds
99.99% <= 20 milliseconds
99.99% <= 21 milliseconds
99.99% <= 22 milliseconds
99.99% <= 24 milliseconds
99.99% <= 26 milliseconds
99.99% <= 27 milliseconds
99.99% <= 28 milliseconds
100.00% <= 29 milliseconds
100.00% <= 30 milliseconds
100.00% <= 31 milliseconds
100.00% <= 32 milliseconds
100.00% <= 34 milliseconds
100.00% <= 35 milliseconds
30892.80 requests per second
 
====== LPUSH (needed to benchmark LRANGE) ======
  100000 requests completed in 3.04 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1
 
1.69% <= 1 milliseconds
53.14% <= 2 milliseconds
99.17% <= 3 milliseconds
99.85% <= 4 milliseconds
99.91% <= 5 milliseconds
99.97% <= 6 milliseconds
99.97% <= 7 milliseconds
99.98% <= 9 milliseconds
99.98% <= 10 milliseconds
99.98% <= 11 milliseconds
99.98% <= 12 milliseconds
99.98% <= 13 milliseconds
99.98% <= 14 milliseconds
99.98% <= 15 milliseconds
99.98% <= 17 milliseconds
99.99% <= 18 milliseconds
99.99% <= 20 milliseconds
99.99% <= 21 milliseconds
99.99% <= 22 milliseconds
99.99% <= 23 milliseconds
99.99% <= 24 milliseconds
99.99% <= 25 milliseconds
99.99% <= 26 milliseconds
99.99% <= 28 milliseconds
100.00% <= 31 milliseconds
100.00% <= 32 milliseconds
100.00% <= 33 milliseconds
100.00% <= 34 milliseconds
100.00% <= 34 milliseconds
32894.74 requests per second
 
====== LRANGE_100 (first 100 elements) ======
  100000 requests completed in 5.70 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1
 
1.70% <= 1 milliseconds
54.19% <= 2 milliseconds
91.25% <= 3 milliseconds
98.11% <= 4 milliseconds
99.26% <= 5 milliseconds
99.62% <= 6 milliseconds
99.79% <= 7 milliseconds
99.88% <= 8 milliseconds
99.93% <= 9 milliseconds
99.94% <= 10 milliseconds
99.96% <= 11 milliseconds
99.96% <= 12 milliseconds
99.97% <= 13 milliseconds
99.97% <= 14 milliseconds
99.98% <= 16 milliseconds
99.98% <= 17 milliseconds
99.98% <= 18 milliseconds
99.98% <= 19 milliseconds
99.99% <= 20 milliseconds
99.99% <= 22 milliseconds
99.99% <= 23 milliseconds
99.99% <= 25 milliseconds
99.99% <= 26 milliseconds
99.99% <= 28 milliseconds
99.99% <= 30 milliseconds
99.99% <= 31 milliseconds
99.99% <= 34 milliseconds
100.00% <= 35 milliseconds
100.00% <= 36 milliseconds
100.00% <= 37 milliseconds
100.00% <= 38 milliseconds
100.00% <= 39 milliseconds
100.00% <= 40 milliseconds
17528.48 requests per second
 
====== LRANGE_300 (first 300 elements) ======
  100000 requests completed in 12.58 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1
 
0.00% <= 1 milliseconds
0.36% <= 2 milliseconds
23.51% <= 3 milliseconds
79.53% <= 4 milliseconds
92.58% <= 5 milliseconds
96.18% <= 6 milliseconds
98.00% <= 7 milliseconds
98.81% <= 8 milliseconds
99.24% <= 9 milliseconds
99.52% <= 10 milliseconds
99.66% <= 11 milliseconds
99.79% <= 12 milliseconds
99.83% <= 13 milliseconds
99.85% <= 14 milliseconds
99.86% <= 15 milliseconds
99.89% <= 16 milliseconds
99.91% <= 17 milliseconds
99.92% <= 18 milliseconds
99.93% <= 19 milliseconds
99.94% <= 20 milliseconds
99.96% <= 21 milliseconds
99.96% <= 22 milliseconds
99.97% <= 23 milliseconds
99.97% <= 24 milliseconds
99.98% <= 25 milliseconds
99.98% <= 26 milliseconds
99.99% <= 27 milliseconds
99.99% <= 29 milliseconds
100.00% <= 30 milliseconds
100.00% <= 31 milliseconds
100.00% <= 32 milliseconds
100.00% <= 34 milliseconds
7947.23 requests per second
 
====== LRANGE_500 (first 450 elements) ======
  100000 requests completed in 16.72 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1
 
0.00% <= 1 milliseconds
0.00% <= 2 milliseconds
0.30% <= 3 milliseconds
26.18% <= 4 milliseconds
77.96% <= 5 milliseconds
90.88% <= 6 milliseconds
94.68% <= 7 milliseconds
97.69% <= 8 milliseconds
99.05% <= 9 milliseconds
99.52% <= 10 milliseconds
99.72% <= 11 milliseconds
99.83% <= 12 milliseconds
99.91% <= 13 milliseconds
99.94% <= 14 milliseconds
99.97% <= 15 milliseconds
99.99% <= 16 milliseconds
99.99% <= 17 milliseconds
100.00% <= 18 milliseconds
100.00% <= 19 milliseconds
100.00% <= 19 milliseconds
5980.50 requests per second
 
====== LRANGE_600 (first 600 elements) ======
  100000 requests completed in 20.93 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1
 
0.00% <= 2 milliseconds
0.01% <= 3 milliseconds
0.57% <= 4 milliseconds
30.41% <= 5 milliseconds
79.57% <= 6 milliseconds
92.39% <= 7 milliseconds
96.23% <= 8 milliseconds
98.32% <= 9 milliseconds
99.28% <= 10 milliseconds
99.64% <= 11 milliseconds
99.77% <= 12 milliseconds
99.82% <= 13 milliseconds
99.85% <= 14 milliseconds
99.87% <= 15 milliseconds
99.88% <= 16 milliseconds
99.88% <= 17 milliseconds
99.89% <= 18 milliseconds
99.92% <= 19 milliseconds
99.92% <= 20 milliseconds
99.94% <= 21 milliseconds
99.95% <= 22 milliseconds
99.95% <= 24 milliseconds
99.95% <= 26 milliseconds
99.95% <= 27 milliseconds
99.96% <= 30 milliseconds
99.96% <= 31 milliseconds
99.96% <= 32 milliseconds
99.96% <= 33 milliseconds
99.96% <= 34 milliseconds
99.96% <= 36 milliseconds
99.97% <= 38 milliseconds
99.97% <= 39 milliseconds
99.97% <= 40 milliseconds
99.98% <= 41 milliseconds
99.98% <= 503 milliseconds
99.98% <= 504 milliseconds
100.00% <= 505 milliseconds
100.00% <= 505 milliseconds
4776.92 requests per second
 
====== MSET (10 keys) ======
  100000 requests completed in 4.71 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1
 
1.03% <= 1 milliseconds
29.24% <= 2 milliseconds
92.22% <= 3 milliseconds
98.38% <= 4 milliseconds
99.60% <= 5 milliseconds
99.83% <= 6 milliseconds
99.90% <= 7 milliseconds
99.92% <= 8 milliseconds
99.92% <= 9 milliseconds
99.92% <= 10 milliseconds
99.92% <= 11 milliseconds
99.92% <= 13 milliseconds
99.92% <= 14 milliseconds
99.92% <= 15 milliseconds
99.93% <= 16 milliseconds
99.93% <= 18 milliseconds
99.93% <= 20 milliseconds
99.93% <= 22 milliseconds
99.93% <= 23 milliseconds
99.93% <= 24 milliseconds
99.93% <= 25 milliseconds
99.93% <= 27 milliseconds
99.93% <= 28 milliseconds
99.93% <= 29 milliseconds
99.94% <= 30 milliseconds
99.94% <= 31 milliseconds
99.94% <= 33 milliseconds
99.94% <= 34 milliseconds
99.94% <= 35 milliseconds
99.94% <= 37 milliseconds
99.94% <= 38 milliseconds
99.94% <= 42 milliseconds
99.94% <= 44 milliseconds
99.94% <= 45 milliseconds
99.95% <= 49 milliseconds
99.95% <= 51 milliseconds
99.95% <= 54 milliseconds
99.95% <= 56 milliseconds
99.95% <= 57 milliseconds
99.95% <= 59 milliseconds
99.95% <= 1022 milliseconds
99.96% <= 1023 milliseconds
99.99% <= 1024 milliseconds
100.00% <= 1024 milliseconds

21222.41 requests per second

Windows版Redis如何使用?(单机)的更多相关文章

  1. MS Open Tech 技术团队构建可靠的Windows版Redis

    可靠的Windows版Redis 副标题: 评论更精彩,教你怎么解决64位Windows版Redis狂占C盘的问题. MS Open Tech 技术团队最近花了很多时间来测试最新构建的Windows版 ...

  2. 硬盘杀手!Windows版Redis疯狂占用C盘空间!

    关键词:Redis占用C盘,Windows Redis,64位Windows版Redis疯狂占用C盘空间,redis启动后创建RedisQFolk_****.dat文件.redis-server.ex ...

  3. .net core 使用windows版redis

    在项目中为了减少程序占用内存(将结果保存在全局变量里面,会占用内存),要求使用redis.开始了爬坑的过程.o(╥﹏╥)o c#操作redis 基本就这3中情况: ServiceStack.Redis ...

  4. 硬盘杀手!Windows版Redis疯狂占用C盘空间【转】

    [问题的原因] Windows版Redis启动后,会在C盘自动创建一个很大的文件,C:\Users\{你的用户名}\AppData\Local\Redis\RedisQFolk_****.dat 我们 ...

  5. 可靠的Windows版Redis

    副标题: 评论更精彩,教你怎么解决64位Windows版Redis狂占C盘的问题. MS Open Tech 技术团队近期花了非常多时间来測试最新构建的Windows版Redis(可在 MS Open ...

  6. 使用 Redis 源码编译发布 Windows 版 Redis For Windows 发行包

    Redis 是个高性能的键值数据库,现在日常项目开发过程中,目前个人开发项目基本都会用到 Redis,主要是用来做 缓存 和 分布式锁 的底层支持,个人喜欢用 .NET 技术体系,所以一般部署也是用 ...

  7. 下载安装windows版Redis

    链接       https://github.com/MicrosoftArchive/redis/releases 选择版本下载 在redis目录打开cmd命令输入 redis-server.ex ...

  8. Windows版Redis主从配置

    一.下载 从github上下载Redis的zip包,地址:https://github.com/MicrosoftArchive/redis/releases Redis本身不支持windows,这是 ...

  9. windows版redis报错:本地计算机上的Redis服务启动后停止

    解决 1.如果需要临时启动Redis 使用命令:redis-server.exe   redis.windows.conf   --maxheap 200m 说明:200m是指定最大堆内存是200m, ...

随机推荐

  1. java生成6位随机数的5种方法

    转自:https://blog.csdn.net/u012491783/article/details/76862526/

  2. C# 遍历文件夹及子目录下所有图片.

    要求:取指定目录下面的所有图片,以表格的型式展示并显示该图片的相对路径. 服务端代码: public partial class ViewIcon : System.Web.UI.Page { JAr ...

  3. maven 项目加载本地JAR

     将jar安装到本地的maven仓库 1.首先确定本地有maven环境. 2.安装本地jar 模板: mvn install:install-file -Dfile=<path-to-file& ...

  4. Jquery validform

    一.validform是什么?            validform是一款智能的表单验证js插件,它是基于jQuery库与css,我们只需要把表单对象放入,             就可以对整个表 ...

  5. Python使用functools模块中的partial函数生成偏函数

    所谓偏函数即是规定了固定参数的函数,在函数式编程中我们经常可以用到,这里我们就来看一下Python使用functools模块中的partial函数生成偏函数的方法 python 中提供一种用于对函数固 ...

  6. Spark RDD概念学习系列之如何创建RDD

    不多说,直接上干货! 创建RDD 方式一:从集合创建RDD (1)makeRDD (2)Parallelize 注意:makeRDD可以指定每个分区perferredLocations参数,而para ...

  7. The German Collegiate Programming Contest 2017

    B - Building 给一个m各面的多边形柱体,每一侧面有n*n个格子,现在对这些格子染色,看有多少种方式使得多面柱体无论如何旋转都不会与另一个一样. #include <bits/stdc ...

  8. NTP同步底层实现

    RFC http://www.ietf.org/rfc/rfc5905.txt https://www.eecis.udel.edu/~mills/ntp/html/select.html https ...

  9. [USACO18JAN] MooTube (离线并查集)

    题目大意:给你一棵边权树,定义两点间距离为它们唯一路径上的最小路权,求与某点距离不大于K(k为已知)的点的数量 带权并查集维护集合内元素总数 路和问题 都按权值大到小排序,枚举问题, 建权值不小于K的 ...

  10. 页面关闭或刷新时触发javascript的事件

    当页面在关闭或刷新时提示 window.onbeforeunload(function(){ //判断是关闭还是刷新 1.满足关闭,否则是刷新 if(event.clientX>document ...