最近测试服务端的时候，接触到了redis，之前也看过，但不系统，借着这次实践，记录一下。
一、写在前面
Redis是一个开源的使用ANSI C语言编写、遵守BSD协议、支持网络、可基于内存亦可持久化的日志型、Key-Value数据库，并提供多种语言的API。
它通常被称为数据结构服务器，因为值（value）可以是 字符串(String), 哈希(Map), 列表(list), 集合(sets) 和 有序集合(sorted sets)等类型。
使用场景和优势简单概述：
1.redis是目前业界非常受到欢迎的一个内存数据库，一般用作系统的中间缓存系统，用以提升整体商业系统的吞吐量和响应速度；
2.redis支持从内存中实现数据的读写，所以速度非常快；
3.redis支持数据持久化，redis将数据存储在硬盘中，即使断电了，redis依然可以将数据重新加载到内存中。
二、安装redis
windows、linux系统下安装redis的详细教程可以见此链接：
http://www.runoob.com/redis/redis-install.html
下载完之后，进行解压、安装：
解压命令：tar -zxvf redis-3.2.11.tar.gz
解压得到一个【redis-3.2.11】文件夹，进入到此文件夹内；
Linux系统安装步骤：
1.输入指令：make，进行编译，编译完成之后，会看到：
然后cd到src目录
2.执行make install，进行安装
make install PREFIX=/usr/local/redis #安装到指定目录中
如果make失败，一般是你们系统中还未安装gcc或者tcl（根据具体的报错信息安装），那么可以通过yum安装：
yum install gcc/tcl
安装完成后，继续执行make
在安装redis成功后，可以在/usr/local/redis看到一个bin的目录，里面包括了以下文件：
redis-benchmark redis-check-aof redis-check-dump redis-cli redis-server
测试安装是否成功
[root@docker redis-3.2.11]# make test
只截取最后的结果：
\o/ All tests passed without errors!
Cleanup: may take some time... OK
配置redis.conf：
[root@docker redis-3.2.11]# vi /usr/local/src/redis-3.2.11/redis.conf
我这里修改3个地方
A. daemonize no 改成 daemonize yes （将redis修改为后台启动进程，防止redis启动后一直停留在redis界面）
B. logfile "" 改成 logfile "./redis.log"（redis日志文件，在redis.conf同级目录下）
C. bind 127.0.0.1 （只能本机访问） 改为 bind 0.0.0.0 （非本机亦可访问（或者可以绑定指定IP））
启动redis:
[root@docker ~]# redis-server /usr/local/src/redis-3.2.11/redis.conf
这里加载刚才修改的默认的redis配置文件redis.conf
查看是否启动成功:
[root@docker ~]# ps -ef | grep redis
root 30284 1 0 16:48 ? 00:00:00 redis-server 127.0.0.1:6379
root 30289 25916 0 16:48 pts/0 00:00:00 grep redis
测试redis:
[root@docker ~]# redis-cli
127.0.0.1:6379> set foo bar
OK
127.0.0.1:6379> get foo
"bar"
127.0.0.1:6379> exit
关闭redis:
[root@docker redis-3.2.11]# redis-cli shutdown
redis安全模式访问:
测试程序报错为：
DENIED Redis is running protected mode because protected mode is enabled,
no bind address was specified, no authentication password is requested to clients.
In this mode connections are only accepted from the loopback interface.
需要给redis配置密码
启动redis客户端
执行 redis-cli指令
然后执行 config set requirepass 777888（密码）
三、redis测试
1.简单的Redis测试程序:
可以自行创建Eclipse项目，引入jedis的客户端包，测试程序如下：
import redis.clients.jedis.Jedis;
import redis.clients.jedis.exceptions.JedisConnectionException;
public class RedisTest {
private Jedis jedis = null;
private String key1 = "key1";
private String key2 = "key2";
public RedisTest() {
jedis = new Jedis("127.0.0.1"); // redis的IP地址
jedis.auth("redis"); // redis密码
}
public static void main(String[] args) {
RedisTest redisTest = new RedisTest();
redisTest.isReachable(); // redis是否访问成功 返回结果true/false
redisTest.testData(); // 数据测试
redisTest.delData(); // 删除数据
redisTest.testExpire();
}
public boolean isReachable() {
boolean isReached = true;
try {
jedis.connect();
jedis.ping();
// jedis.quit();
} catch (JedisConnectionException e) {
e.printStackTrace();
isReached = false;
}
System.out
.println("The current Redis Server is Reachable:" + isReached);
return isReached;
}
public void testData() {
jedis.set("key1", "data1");
jedis.set("maxm", "MMM");
System.out.println(jedis.get("maxm"));
System.out.println("Check status of data existing:"
+ jedis.exists(key1));
System.out.println("Get Data key1:" + jedis.get("key1"));
long s = jedis.sadd(key2, "data2");
System.out.println("Add key2 Data:" + jedis.scard(key2)
+ " with status " + s);
}
public void delData() {
long count = jedis.del(key1);
System.out.println("Get Data Key1 after it is deleted:"
+ jedis.get(key1));
}
public void testExpire() {
long count = jedis.expire(key2, 5);
try {
Thread.currentThread().sleep(6000);
} catch (InterruptedException e) {
e.printStackTrace();
}
if (jedis.exists(key2)) {
System.out
.println("Get Key2 in Expire Action:" + jedis.scard(key2));
} else {
System.out.println("Key2 is expired with value:"
+ jedis.scard(key2));
}
}
}
2.Redis性能压测工具 redis-benchmark
Redis 自带了一个叫 redis-benchmark 的工具来模拟 N 个客户端同时发出 M 个请求。 （类似于 Apache ab 程序）。你可以使用 redis-benchmark -h 来查看基准参数。
以下参数被支持： Usage: redis-benchmark [-h <host>] [-p <port>] [-c <clients>] [-n <requests]> [-k <boolean>] -h <hostname> Server hostname (default 127.0.0.1)
-p <port> Server port (default 6379)
-s <socket> Server socket (overrides host and port)
-a <password> Password for Redis Auth
-c <clients> Number of parallel connections (default 50)
-n <requests> Total number of requests (default 100000)
-d <size> Data size of SET/GET value in bytes (default 2)
-dbnum <db> SELECT the specified db number (default 0)
-k <boolean> 1=keep alive 0=reconnect (default 1)
-r <keyspacelen> Use random keys for SET/GET/INCR, random values for SADD
Using this option the benchmark will expand the string __rand_int__
inside an argument with a 12 digits number in the specified range
from 0 to keyspacelen-1. The substitution changes every time a command
is executed. Default tests use this to hit random keys in the
specified range.
-P <numreq> Pipeline <numreq> requests. Default 1 (no pipeline).
-q Quiet. Just show query/sec values
--csv Output in CSV format
-l Loop. Run the tests forever
-t <tests> Only run the comma separated list of tests. The test
names are the same as the ones produced as output.
-I Idle mode. Just open N idle connections and wait.
测试命令事例：
1、redis-benchmark -h 192.168.1.201 -p 6379 -c 100 -n 100000
100个并发连接，100000个请求，检测host为localhost 端口为6379的redis服务器性能
2、redis-benchmark -h 192.168.1.201 -p 6379 -q -d 100
测试存取大小为100字节的数据包的性能
3、redis-benchmark -t set,lpush -n 100000 -q
只测试某些操作的性能
4、redis-benchmark -n 100000 -q script load "redis.call('set','foo','bar')"
只测试某些数值存取的性能
requests completed in 0.30 seconds
parallel clients
bytes payload
keep alive: 1 0.11% <= 1 milliseconds
86.00% <= 2 milliseconds
90.12% <= 3 milliseconds
96.68% <= 4 milliseconds
99.27% <= 5 milliseconds
99.54% <= 6 milliseconds
99.69% <= 7 milliseconds
99.78% <= 8 milliseconds
99.89% <= 9 milliseconds
100.00% <= 9 milliseconds
33222.59 requests per second ====== PING_BULK ======
requests completed in 0.27 seconds
parallel clients
bytes payload
keep alive: 1 0.93% <= 1 milliseconds
97.66% <= 2 milliseconds
100.00% <= 2 milliseconds
37174.72 requests per second ====== SET ======
requests completed in 0.32 seconds
parallel clients
bytes payload
keep alive: 1 0.22% <= 1 milliseconds
91.68% <= 2 milliseconds
97.78% <= 3 milliseconds
98.80% <= 4 milliseconds
99.38% <= 5 milliseconds
99.61% <= 6 milliseconds
99.72% <= 7 milliseconds
99.83% <= 8 milliseconds
99.94% <= 9 milliseconds
100.00% <= 9 milliseconds
30959.75 requests per second ====== GET ======
requests completed in 0.28 seconds
parallel clients
bytes payload
keep alive: 1 0.55% <= 1 milliseconds
98.86% <= 2 milliseconds
100.00% <= 2 milliseconds
35971.22 requests per second ====== INCR ======
requests completed in 0.14 seconds
parallel clients
bytes payload
keep alive: 1 95.61% <= 1 milliseconds
100.00% <= 1 milliseconds
69444.45 requests per second ====== LPUSH ======
requests completed in 0.21 seconds
parallel clients
bytes payload
keep alive: 1 18.33% <= 1 milliseconds
100.00% <= 1 milliseconds
48309.18 requests per second ====== LPOP ======
requests completed in 0.23 seconds
parallel clients
bytes payload
keep alive: 1 0.29% <= 1 milliseconds
99.76% <= 2 milliseconds
100.00% <= 2 milliseconds
44052.86 requests per second ====== SADD ======
requests completed in 0.22 seconds
parallel clients
bytes payload
keep alive: 1 2.37% <= 1 milliseconds
99.81% <= 2 milliseconds
100.00% <= 2 milliseconds
44444.45 requests per second ====== SPOP ======
requests completed in 0.22 seconds
parallel clients
bytes payload
keep alive: 1 4.27% <= 1 milliseconds
99.84% <= 2 milliseconds
100.00% <= 2 milliseconds
44642.86 requests per second ====== LPUSH (needed to benchmark LRANGE) ======
requests completed in 0.22 seconds
parallel clients
bytes payload
keep alive: 1 12.35% <= 1 milliseconds
99.62% <= 2 milliseconds
100.00% <= 2 milliseconds
46082.95 requests per second ====== LRANGE_100 (first 100 elements) ======
requests completed in 0.48 seconds
parallel clients
bytes payload
keep alive: 1 0.01% <= 1 milliseconds
3.27% <= 2 milliseconds
98.71% <= 3 milliseconds
99.93% <= 4 milliseconds
100.00% <= 4 milliseconds
20964.36 requests per second ====== LRANGE_300 (first 300 elements) ======
requests completed in 1.26 seconds
parallel clients
bytes payload
keep alive: 1 0.01% <= 2 milliseconds
0.14% <= 3 milliseconds
0.90% <= 4 milliseconds
7.03% <= 5 milliseconds
31.68% <= 6 milliseconds
78.93% <= 7 milliseconds
98.88% <= 8 milliseconds
99.56% <= 9 milliseconds
99.72% <= 10 milliseconds
99.95% <= 11 milliseconds
100.00% <= 11 milliseconds
7961.78 requests per second ====== LRANGE_500 (first 450 elements) ======
requests completed in 1.82 seconds
parallel clients
bytes payload
keep alive: 1 0.01% <= 2 milliseconds
0.06% <= 3 milliseconds
0.14% <= 4 milliseconds
0.30% <= 5 milliseconds
0.99% <= 6 milliseconds
2.91% <= 7 milliseconds
8.11% <= 8 milliseconds
43.15% <= 9 milliseconds
88.38% <= 10 milliseconds
97.25% <= 11 milliseconds
98.61% <= 12 milliseconds
99.26% <= 13 milliseconds
99.30% <= 14 milliseconds
99.44% <= 15 milliseconds
99.48% <= 16 milliseconds
99.64% <= 17 milliseconds
99.85% <= 18 milliseconds
99.92% <= 19 milliseconds
99.95% <= 20 milliseconds
99.96% <= 21 milliseconds
99.97% <= 22 milliseconds
100.00% <= 23 milliseconds
5491.49 requests per second ====== LRANGE_600 (first 600 elements) ======
requests completed in 2.29 seconds
parallel clients
bytes payload
keep alive: 1 0.01% <= 2 milliseconds
0.05% <= 3 milliseconds
0.10% <= 4 milliseconds
0.19% <= 5 milliseconds
0.34% <= 6 milliseconds
0.46% <= 7 milliseconds
0.58% <= 8 milliseconds
4.46% <= 9 milliseconds
21.80% <= 10 milliseconds
40.48% <= 11 milliseconds
60.14% <= 12 milliseconds
79.81% <= 13 milliseconds
93.77% <= 14 milliseconds
97.14% <= 15 milliseconds
98.67% <= 16 milliseconds
99.08% <= 17 milliseconds
99.30% <= 18 milliseconds
99.41% <= 19 milliseconds
99.52% <= 20 milliseconds
99.61% <= 21 milliseconds
99.79% <= 22 milliseconds
99.88% <= 23 milliseconds
99.89% <= 24 milliseconds
99.95% <= 26 milliseconds
99.96% <= 27 milliseconds
99.97% <= 28 milliseconds
99.98% <= 29 milliseconds
100.00% <= 29 milliseconds
4359.20 requests per second ====== MSET (10 keys) ======
requests completed in 0.37 seconds
parallel clients
bytes payload
keep alive: 1 0.01% <= 1 milliseconds
2.00% <= 2 milliseconds
18.41% <= 3 milliseconds
88.55% <= 4 milliseconds
96.09% <= 5 milliseconds
99.50% <= 6 milliseconds
99.65% <= 7 milliseconds
99.75% <= 8 milliseconds
99.77% <= 9 milliseconds
99.78% <= 11 milliseconds
99.79% <= 12 milliseconds
99.80% <= 13 milliseconds
99.81% <= 15 milliseconds
99.82% <= 16 milliseconds
99.83% <= 17 milliseconds
99.84% <= 19 milliseconds
99.85% <= 21 milliseconds
99.86% <= 23 milliseconds
99.87% <= 24 milliseconds
99.88% <= 25 milliseconds
99.89% <= 27 milliseconds
99.90% <= 28 milliseconds
99.91% <= 30 milliseconds
99.92% <= 32 milliseconds
99.93% <= 34 milliseconds
99.95% <= 35 milliseconds
99.96% <= 36 milliseconds
99.97% <= 37 milliseconds
99.98% <= 39 milliseconds
99.99% <= 41 milliseconds
100.00% <= 41 milliseconds
27173.91 requests per second
更详细的使用方法可以参加链接：
http://www.redis.cn/topics/benchmarks.html
-------------------------------------------
***番外篇***：
一、将redis做成一个服务
复制脚本到/etc/rc.d/init.d目录
ps: /etc/rc.d/init.d/目录下的脚本就类似与windows中的注册表，在系统启动的时候某些指定脚本将被执行
其服务脚本位于：
/usr/local/src/redis/utils/redis_init_script
必须将其复制到/etc/rc.d/init.d的目录下：
cp /usr/local/src/redis/utils/redis_init_script /etc/rc.d/init.d/redis
将redis_init_script复制到/etc/rc.d/init.d/，同时易名为redis。
如果这时添加注册服务：
chkconfig --add redis
将报以下错误：
redis服务不支持chkconfig
为此，需要更改redis脚本。
2.更改redis脚本
打开使用vi打开脚本，查看脚本信息：
vim /etc/rc.d/init.d/redis
看到的内容如下(下内容是更改好的信息)：
#!/bin/sh
#chkconfig: 2345 80 90
# Simple Redis init.d script conceived to work on Linux systems
# as it does use of the /proc filesystem. REDISPORT=6379
EXEC=/usr/local/redis/bin/redis-server
CLIEXEC=/usr/local/redis/bin/redis-cli PIDFILE=/var/run/redis_${REDISPORT}.pid
CONF="/etc/redis/${REDISPORT}.conf" case "$1" in
start)
if [ -f $PIDFILE ]
then
echo "$PIDFILE exists, process is already running or crashed"
else
echo "Starting Redis server..."
$EXEC $CONF &
fi
;;
stop)
if [ ! -f $PIDFILE ]
then
echo "$PIDFILE does not exist, process is not running"
else
PID=$(cat $PIDFILE)
echo "Stopping ..."
$CLIEXEC -p $REDISPORT shutdown
while [ -x /proc/${PID} ]
do
echo "Waiting for Redis to shutdown ..."
sleep 1
done
echo "Redis stopped"
fi
;;
*)
echo "Please use start or stop as first argument"
;;
esac
和原配置文件相比：
1.新增了第2行的内容
#chkconfig: 2345 80 90
2.原文件EXEC、CLIEXEC参数，有所更改。
EXEC=/usr/local/redis/bin/redis-server
CLIEXEC=/usr/local/redis/bin/redis-cli
3.redis开启的命令，以后台运行的方式执行。
$EXEC $CONF &
ps:注意后面的那个“&”，即是将服务转到后面运行的意思，否则启动服务时，Redis服务将
占据在前台，占用了主用户界面，造成其它的命令执行不了。
4.将redis配置文件拷贝到/etc/redis/${REDISPORT}.conf
mkdir /etc/redis
cp /usr/local/src/redis/redis.conf /etc/redis/6379.conf
这样，redis服务脚本指定的CONF就存在了。默认情况下，Redis未启用认证，可以通过开启6379.conf的requirepass 指定一个验证密码。
以上操作完成后，即可注册yedis服务：
chkconfig --add redis
5.启动redis服务
service redis start
二、将Redis的命令所在目录添加到系统参数PATH中 （添加环境变量）
修改profile文件：
vi /etc/profile
在最后行追加:
export PATH="$PATH:/usr/local/redis/bin"
然后马上应用这个文件：
. /etc/profile
这样就可以直接调用redis-cli的命令了，如下所示：
$ redis-cli
redis 127.0.0.1:6379> auth superman
OK
redis 127.0.0.1:6379> ping
PONG
redis 127.0.0.1:6379>