博客
关于我
强烈建议你试试无所不能的chatGPT,快点击我
Redis的Java客户端Jedis的八种调用方式(事务、管道、分布式…)介绍(转)
阅读量:7290 次
发布时间:2019-06-30

本文共 11172 字,大约阅读时间需要 37 分钟。

  1. redis是一个著名的key-value存储系统,而作为其官方推荐的java版客户端jedis也非常强大和稳定,支持事务、管道及有jedis自身实现的分布式。

    在这里对jedis关于事务、管道和分布式的调用方式做一个简单的介绍和对比:

    一、普通同步方式

    最简单和基础的调用方式,

    @Testpublic void test1Normal() {    Jedis jedis = new Jedis("localhost");    long start = System.currentTimeMillis();    for (int i = 0; i < 100000; i++) {        String result = jedis.set("n" + i, "n" + i);    }    long end = System.currentTimeMillis();    System.out.println("Simple SET: " + ((end - start)/1000.0) + " seconds");    jedis.disconnect();}

    很简单吧,每次set之后都可以返回结果,标记是否成功。

    二、事务方式(Transactions)

    redis的事务很简单,他主要目的是保障,一个client发起的事务中的命令可以连续的执行,而中间不会插入其他client的命令。

    看下面例子:

    @Testpublic void test2Trans() {    Jedis jedis = new Jedis("localhost");    long start = System.currentTimeMillis();    Transaction tx = jedis.multi();    for (int i = 0; i < 100000; i++) {        tx.set("t" + i, "t" + i);    }    List results = tx.exec();    long end = System.currentTimeMillis();    System.out.println("Transaction SET: " + ((end - start)/1000.0) + " seconds");    jedis.disconnect();}

    我们调用jedis.watch(…)方法来监控key,如果调用后key值发生变化,则整个事务会执行失败。另外,事务中某个操作失败,并不会回滚其他操作。这一点需要注意。还有,我们可以使用discard()方法来取消事务。

    三、管道(Pipelining)

    有时,我们需要采用异步方式,一次发送多个指令,不同步等待其返回结果。这样可以取得非常好的执行效率。这就是管道,调用方法如下:

    @Testpublic void test3Pipelined() {    Jedis jedis = new Jedis("localhost");    Pipeline pipeline = jedis.pipelined();    long start = System.currentTimeMillis();    for (int i = 0; i < 100000; i++) {        pipeline.set("p" + i, "p" + i);    }    List results = pipeline.syncAndReturnAll();    long end = System.currentTimeMillis();    System.out.println("Pipelined SET: " + ((end - start)/1000.0) + " seconds");    jedis.disconnect();}

    四、管道中调用事务

    就Jedis提供的方法而言,是可以做到在管道中使用事务,其代码如下:

    @Testpublic void test4combPipelineTrans() {    jedis = new Jedis("localhost");     long start = System.currentTimeMillis();    Pipeline pipeline = jedis.pipelined();    pipeline.multi();    for (int i = 0; i < 100000; i++) {        pipeline.set("" + i, "" + i);    }    pipeline.exec();    List results = pipeline.syncAndReturnAll();    long end = System.currentTimeMillis();    System.out.println("Pipelined transaction: " + ((end - start)/1000.0) + " seconds");    jedis.disconnect();}

    但是经测试(见本文后续部分),发现其效率和单独使用事务差不多,甚至还略微差点。

    五、分布式直连同步调用

    @Testpublic void test5shardNormal() {    List
    shards = Arrays.asList( new JedisShardInfo("localhost",6379), new JedisShardInfo("localhost",6380)); ShardedJedis sharding = new ShardedJedis(shards); long start = System.currentTimeMillis(); for (int i = 0; i < 100000; i++) { String result = sharding.set("sn" + i, "n" + i); } long end = System.currentTimeMillis(); System.out.println("Simple@Sharing SET: " + ((end - start)/1000.0) + " seconds"); sharding.disconnect();}

    这个是分布式直接连接,并且是同步调用,每步执行都返回执行结果。类似地,还有异步管道调用。

    六、分布式直连异步调用

    @Testpublic void test6shardpipelined() {    List
    shards = Arrays.asList( new JedisShardInfo("localhost",6379), new JedisShardInfo("localhost",6380)); ShardedJedis sharding = new ShardedJedis(shards); ShardedJedisPipeline pipeline = sharding.pipelined(); long start = System.currentTimeMillis(); for (int i = 0; i < 100000; i++) { pipeline.set("sp" + i, "p" + i); } List
    results = pipeline.syncAndReturnAll(); long end = System.currentTimeMillis(); System.out.println("Pipelined@Sharing SET: " + ((end - start)/1000.0) + " seconds"); sharding.disconnect();}

    七、分布式连接池同步调用

    如果,你的分布式调用代码是运行在线程中,那么上面两个直连调用方式就不合适了,因为直连方式是非线程安全的,这个时候,你就必须选择连接池调用。

    @Testpublic void test7shardSimplePool() {    List
    shards = Arrays.asList( new JedisShardInfo("localhost",6379), new JedisShardInfo("localhost",6380)); ShardedJedisPool pool = new ShardedJedisPool(new JedisPoolConfig(), shards); ShardedJedis one = pool.getResource(); long start = System.currentTimeMillis(); for (int i = 0; i < 100000; i++) { String result = one.set("spn" + i, "n" + i); } long end = System.currentTimeMillis(); pool.returnResource(one); System.out.println("Simple@Pool SET: " + ((end - start)/1000.0) + " seconds"); pool.destroy();}

    上面是同步方式,当然还有异步方式。

    八、分布式连接池异步调用

    @Testpublic void test8shardPipelinedPool() {    List
    shards = Arrays.asList( new JedisShardInfo("localhost",6379), new JedisShardInfo("localhost",6380)); ShardedJedisPool pool = new ShardedJedisPool(new JedisPoolConfig(), shards); ShardedJedis one = pool.getResource(); ShardedJedisPipeline pipeline = one.pipelined(); long start = System.currentTimeMillis(); for (int i = 0; i < 100000; i++) { pipeline.set("sppn" + i, "n" + i); } List
    results = pipeline.syncAndReturnAll(); long end = System.currentTimeMillis(); pool.returnResource(one); System.out.println("Pipelined@Pool SET: " + ((end - start)/1000.0) + " seconds"); pool.destroy();}

    九、需要注意的地方

    1. 事务和管道都是异步模式。在事务和管道中不能同步查询结果。比如下面两个调用,都是不允许的:

      Transaction tx = jedis.multi(); for (int i = 0; i < 100000; i++) {     tx.set("t" + i, "t" + i); } System.out.println(tx.get("t1000").get());  //不允许 List results = tx.exec(); … … Pipeline pipeline = jedis.pipelined(); long start = System.currentTimeMillis(); for (int i = 0; i < 100000; i++) {     pipeline.set("p" + i, "p" + i); } System.out.println(pipeline.get("p1000").get()); //不允许 List results = pipeline.syncAndReturnAll();
    2. 事务和管道都是异步的,个人感觉,在管道中再进行事务调用,没有必要,不如直接进行事务模式。

    3. 分布式中,连接池的性能比直连的性能略好(见后续测试部分)。

    4. 分布式调用中不支持事务。

      因为事务是在服务器端实现,而在分布式中,每批次的调用对象都可能访问不同的机器,所以,没法进行事务。

    十、测试

    运行上面的代码,进行测试,其结果如下:

    Simple SET: 5.227 secondsTransaction SET: 0.5 secondsPipelined SET: 0.353 secondsPipelined transaction: 0.509 secondsSimple@Sharing SET: 5.289 secondsPipelined@Sharing SET: 0.348 secondsSimple@Pool SET: 5.039 secondsPipelined@Pool SET: 0.401 seconds

    另外,经测试分布式中用到的机器越多,调用会越慢。上面是2片,下面是5片:

    Simple@Sharing SET: 5.494 secondsPipelined@Sharing SET: 0.51 secondsSimple@Pool SET: 5.223 secondsPipelined@Pool SET: 0.518 seconds

    下面是10片:

    Simple@Sharing SET: 5.9 secondsPipelined@Sharing SET: 0.794 secondsSimple@Pool SET: 5.624 secondsPipelined@Pool SET: 0.762 seconds

    下面是100片:

    Simple@Sharing SET: 14.055 secondsPipelined@Sharing SET: 8.185 secondsSimple@Pool SET: 13.29 secondsPipelined@Pool SET: 7.767 seconds

    分布式中,连接池方式调用不但线程安全外,根据上面的测试数据,也可以看出连接池比直连的效率更好。

    十一、完整的测试代码

    package com.example.nosqlclient;import java.util.Arrays;import java.util.List;import org.junit.AfterClass;import org.junit.BeforeClass;import org.junit.Test;import redis.clients.jedis.Jedis;import redis.clients.jedis.JedisPoolConfig;import redis.clients.jedis.JedisShardInfo;import redis.clients.jedis.Pipeline;import redis.clients.jedis.ShardedJedis;import redis.clients.jedis.ShardedJedisPipeline;import redis.clients.jedis.ShardedJedisPool;import redis.clients.jedis.Transaction;import org.junit.FixMethodOrder;import org.junit.runners.MethodSorters;@FixMethodOrder(MethodSorters.NAME_ASCENDING)public class TestJedis {    private static Jedis jedis;    private static ShardedJedis sharding;    private static ShardedJedisPool pool;    @BeforeClass    public static void setUpBeforeClass() throws Exception {        List
    shards = Arrays.asList( new JedisShardInfo("localhost",6379), new JedisShardInfo("localhost",6379)); //使用相同的ip:port,仅作测试 jedis = new Jedis("localhost"); sharding = new ShardedJedis(shards); pool = new ShardedJedisPool(new JedisPoolConfig(), shards); } @AfterClass public static void tearDownAfterClass() throws Exception { jedis.disconnect(); sharding.disconnect(); pool.destroy(); } @Test public void test1Normal() { long start = System.currentTimeMillis(); for (int i = 0; i < 100000; i++) { String result = jedis.set("n" + i, "n" + i); } long end = System.currentTimeMillis(); System.out.println("Simple SET: " + ((end - start)/1000.0) + " seconds"); } @Test public void test2Trans() { long start = System.currentTimeMillis(); Transaction tx = jedis.multi(); for (int i = 0; i < 100000; i++) { tx.set("t" + i, "t" + i); } //System.out.println(tx.get("t1000").get()); List
    results = tx.exec(); long end = System.currentTimeMillis(); System.out.println("Transaction SET: " + ((end - start)/1000.0) + " seconds"); } @Test public void test3Pipelined() { Pipeline pipeline = jedis.pipelined(); long start = System.currentTimeMillis(); for (int i = 0; i < 100000; i++) { pipeline.set("p" + i, "p" + i); } //System.out.println(pipeline.get("p1000").get()); List results = pipeline.syncAndReturnAll(); long end = System.currentTimeMillis(); System.out.println("Pipelined SET: " + ((end - start)/1000.0) + " seconds"); } @Test public void test4combPipelineTrans() { long start = System.currentTimeMillis(); Pipeline pipeline = jedis.pipelined(); pipeline.multi(); for (int i = 0; i < 100000; i++) { pipeline.set("" + i, "" + i); } pipeline.exec(); List results = pipeline.syncAndReturnAll(); long end = System.currentTimeMillis(); System.out.println("Pipelined transaction: " + ((end - start)/1000.0) + " seconds"); } @Test public void test5shardNormal() { long start = System.currentTimeMillis(); for (int i = 0; i < 100000; i++) { String result = sharding.set("sn" + i, "n" + i); } long end = System.currentTimeMillis(); System.out.println("Simple@Sharing SET: " + ((end - start)/1000.0) + " seconds"); } @Test public void test6shardpipelined() { ShardedJedisPipeline pipeline = sharding.pipelined(); long start = System.currentTimeMillis(); for (int i = 0; i < 100000; i++) { pipeline.set("sp" + i, "p" + i); } List results = pipeline.syncAndReturnAll(); long end = System.currentTimeMillis(); System.out.println("Pipelined@Sharing SET: " + ((end - start)/1000.0) + " seconds"); } @Test public void test7shardSimplePool() { ShardedJedis one = pool.getResource(); long start = System.currentTimeMillis(); for (int i = 0; i < 100000; i++) { String result = one.set("spn" + i, "n" + i); } long end = System.currentTimeMillis(); pool.returnResource(one); System.out.println("Simple@Pool SET: " + ((end - start)/1000.0) + " seconds"); } @Test public void test8shardPipelinedPool() { ShardedJedis one = pool.getResource(); ShardedJedisPipeline pipeline = one.pipelined(); long start = System.currentTimeMillis(); for (int i = 0; i < 100000; i++) { pipeline.set("sppn" + i, "n" + i); } List results = pipeline.syncAndReturnAll(); long end = System.currentTimeMillis(); pool.returnResource(one); System.out.println("Pipelined@Pool SET: " + ((end - start)/1000.0) + " seconds"); }}
 
 http://blog.csdn.net/zcgsdu/article/details/46912739

 

你可能感兴趣的文章
iOS笔记:进一步认识 ==、isEqual、hash
查看>>
通过 recompose 实现 react router4 权限
查看>>
逻辑思维训练
查看>>
【Golang实现文件服务器】(一)初始版本
查看>>
8年资深测试工程师如何提交有效缺陷
查看>>
代码优化常用方法
查看>>
OkHttp深入分析——基础认知部分
查看>>
组件库webpack构建速度优化经验总结
查看>>
Linux下搭建Redis集群、JedisCluster带密码访问
查看>>
CentOS7下安装Zookeeper-3.4.10
查看>>
敏捷AI | NLP技术在宜信业务中的实践【构建用户画像篇】
查看>>
python版亲戚关系计算器
查看>>
送给程序员们的经典电子书大礼包
查看>>
SQL注入关联分析
查看>>
应用Promise封装Ajax实践
查看>>
渗透&&探测 ( ICMP 篇)
查看>>
容器监控实践—Prometheus的配置与服务发现
查看>>
dubbo源码解析(三十九)集群——merger
查看>>
PAT A1022
查看>>
捋一捋React的生命周期
查看>>