Windows 에서 Redis 설치 사용 강좌

본 고 는 주로 캐 시 기술 중의 Redis 의 설치 와 사용 을 소개 하 는데 참고 하 시기 바 랍 니 다.구체 적 인 내용 은 다음 과 같 습 니 다.
1.Redis for windows 다운로드
인터넷 에서 Redis fow windows 를 검색 하면 Redis 의 압축 패 키 지 를 다운로드 할 수 있다.압축 을 풀다.

이 중 32 비트 와 64 비트 의 서로 다른 버 전의 가방 을 발견 할 수 있 으 며 필요 에 따라 해당 하 는 압축 가방 을 사용 하면 된다.
스트레스 해소
저 는 redisbin 을 사용 합 니 다.x64.zip 압축 패 키 지 를 redis 폴 더 에 압축 해제 합 니 다.

압축 을 풀 면 내용 이.exe 파일 만 있 는 것 을 발견 할 수 있 습 니 다.여기까지,redis 는 반 을 만 든 셈 이다.
배치
redis 다음 에 conf 폴 더 를 새로 만 들 고 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. 
#             ，   no 
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. 
#            ，       pid   
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. 
#     IP 
# bind 127.0.0.1 
 
# Close the connection after a client is idle for N seconds (0 to disable) 
#          ，   0，     。      ，            
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. 
#          ，      ip       
# 
# 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. 
#       ，         ，Redis              key,       ，        ，          。 
# 
# 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. 
#   Redis           ，        ，    ，                   ， 
#   Redis              save      ，                   。 
 
appendonly no 
 
#         
# appendfilename appendonly.aof 
 
# 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 
 
#          
#vm-enabled no; 
 
#         ,    redis   
# vm-swap-file /tmp/redis.swap 
 
#      vm-max-memory          。  vm-max-memory   ，             。 
#    vm-max-memory   0，            。 
# vm-max-memory 0 

4.redis 서버 시작
명령 을 사용 하여 redis 서버 를 시작 합 니 다.
redis-server.exe conf/redis.conf
시작 에 성공 하면 다음 과 같은 힌트 를 볼 수 있 습 니 다.

5.redis 서버 연결
redis 자체 명령 을 사용 하면 서버 에 연결 할 수 있 습 니 다.
redis-cli.exe -h localhost -p 6379
연결 에 성공 하면 다음 과 같은 내용 을 알려 줍 니 다.

이 럴 때,너 는 redis 의 명령 을 사용 하여 데 이 터 를 조작 할 수 있다.기타 지령 은 인터넷 에서 구체 적 으로 살 펴 보 세 요.
이상 은 본문의 전체 내용 이 므 로 여러분 의 학습 에 도움 이 되 기 를 바 랍 니 다.