使用Windows版Redis

1、下载Windows版本的Redis

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

# 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.
daemonize no# 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 1024daemonize no# 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

3、创建redis.bat

redis-server.exe redis.conf

4、进入命令行窗口

5、启动redis

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

7、使用redis

（1）set与get

（2）使用list

lpush, rpush, lpop, rpop, lrange

lrange start end

0 —— 列表第一个元素
-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 
====== 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 
====== PING_INLINE ======100000 requests completed in 2.76 seconds50 parallel clients3 bytes payloadkeep alive: 12.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 seconds50 parallel clients3 bytes payloadkeep alive: 12.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 seconds50 parallel clients3 bytes payloadkeep alive: 12.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 seconds50 parallel clients3 bytes payloadkeep alive: 12.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 seconds50 parallel clients3 bytes payloadkeep alive: 12.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 seconds50 parallel clients3 bytes payloadkeep alive: 11.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 seconds50 parallel clients3 bytes payloadkeep alive: 12.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 seconds50 parallel clients3 bytes payloadkeep alive: 11.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 seconds50 parallel clients3 bytes payloadkeep alive: 12.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 seconds50 parallel clients3 bytes payloadkeep alive: 11.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 seconds50 parallel clients3 bytes payloadkeep alive: 11.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 seconds50 parallel clients3 bytes payloadkeep alive: 10.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 seconds50 parallel clients3 bytes payloadkeep alive: 10.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 seconds50 parallel clients3 bytes payloadkeep alive: 10.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 seconds50 parallel clients3 bytes payloadkeep alive: 11.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 second21222.41 requests per second

使用Windows版Redis相关推荐

  1. Windows版Redis和Redis Desktop Manager安装

    一.Windows版Redis安装 打开redis官网:https://redis.io/download 其实是只有linux版本的,那为什么没有windows版本的呢? 因为redis 是单线程高 ...

  2. windows版 redis安装教程，以及redis客户端安装

    windows版 redis安装教程,以及redis客户端安装 由于这两天安装了redis,在redis挂网上找到的redis都是linux版的,所以在此做个记录,方便以后用,也分享给广大网友 1,w ...

  3. 硬盘杀手！Windows版Redis疯狂占用C盘空间！

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

  4. windows版redis安装使用

    Linux下Redis安装链接 :     转到 redis是一个key-value存储系统.和Memcached类似,它支持存储的value类型相对更多,包括string(字符串).list(链表) ...

  5. windows版redis下载地址

    现在的redis官网没有windows版的下载连了,只能到GitHub下载,地址是: https://github.com/MicrosoftArchive/redis/tags 目前(2018-8- ...

  6. windows版redis

    redis介绍 redis是一款开源的.高性能的键-值存储(key-value store),和memcached类似,redis常被称作是一款key-value内存存储系统或者内存数据库,同时由于它 ...

  7. Windows版redis下载 与 RDM下载

    win版redis下载地址:传送阵 下载后解压 百度网盘下载 链接:https://pan.baidu.com/s/1Tlm_Ho7rp-gHULSWjMtDag 提取码:6rn1 复制这段内容后打开 ...

  8. windows版redis安装教程（2022）

    什么是Redis redis是一个key-value存储系统.和Memcached类似,它支持存储的value类型相对更多,包括string(字符串).list(链表).set(集合)和zset(有序 ...

  9. windows版 redis启动、rabbitMQ启动、kafka启动

    启动redis redis-server.exe redis.windows.conf 失败就 redis-cli.exe shutdown exit 再重启 启动rabbitmq 进sbin rab ...

最新文章

  1. 背单词：3年，34150分钟！
  2. 关于SAP的“Sort key 排序码”
  3. php+curlmultiinit_多线程 - PHP的curl_multi_init并发测试问题
  4. STM32 C/C++ uCOSII 函数调用return 无法返回或者函数无法正常反回上一层函数的问题
  5. 响铃：Don't be evil？Google别闹了
  6. 如何在 ASP.NET Core 中使用 ActionFilter
  7. 拿到大厂Offer了！
  8. .png图片 阴影效果（fliter:drop-shadow属性）案例
  9. 黄章：魅族16s真机非常漂亮 网曝图片与实机相差甚远
  10. elasticsearch 7.0.1 + kibana + elasticsearch-analysis-ik 7.0.0 安装和配置过程中问题备忘录...
  11. 基于(7,4 ) 线性分组码编码和 BPSK 调制
  12. Oracle 同义词详解（synonym）
  13. 雾霾、压力、不良习惯对肌肤的4大危害
  14. 第十三届 蓝桥杯青少年创意编程 C++组 省赛
  15. python中test的用法_Python基础介绍 | 使用pytest进行测试
  16. 高德地图不开位置无法定位服务器,使用高德地图导航时光标不动（定位不动、无法定位）的用户　请进...
  17. crul php 反爬虫,pixabay 反爬好厉害，浏览器能访问，复制所有 headers 用 curl 抓取，直接 403，好神奇！...
  18. rj45管脚定义_“RJ45接口”定义标准是什么？
  19. HTB walkthrough -- Admirer
  20. 简单的学生成绩查询web系统

热门文章

  1. 【nodejs原理源码赏析（3）】欣赏手术级的原型链加工艺术
  2. 华瑞网研（苏州）2014-11部分笔试题（社招）
  3. 计算机图形学E11——B样条曲线
  4. 吴恩达 深度学习 编程作业(2-1.1) Initialization
  5. 面试官、女朋友都满意系列 - 决策树
  6. LeetCode-978：最长湍流子数组
  7. switch VS if else
  8. 基于ViSual Studio 2013 + MYSQL9_5302 + Navicat for MySQL9_5302的ATM自动存取款系统
  9. MATLAB矩阵添加新元素
  10. Node编码格式的设置