using autoflush with AsyncCommands

[jigneshmpatel]

I have implemented the following method:

public void putSetInCacheAsync(Map<String,?> map){
        logger.info("Inside putSetInCacheAsync");
        List<RedisFuture<?>> futures = new ArrayList<>();
        try {
            connection = this.getConnectionFromPool();
            RedisAdvancedClusterAsyncCommands<String, String> asyncCommands = connection.async();
            asyncCommands.setAutoFlushCommands(false);

                for (Map.Entry<String, ?> entry : map.entrySet()) {
                    logger.info("Key: "+entry.getKey());
     
                    futures.add(asyncCommands.set(key,"test");
                   
                   }


                    asyncCommands.flushCommands();


        }
        catch(Exception ece){
            logger.error("Error in putSetInCacheAsync",ece.getMessage());
            throw new Exception(ece.getMessage());
        }
        finally {
            //AwaitAll waits for all of the RedisFutures to complete.
            boolean result = LettuceFutures.awaitAll(5, TimeUnit.SECONDS,
                    futures.toArray(new RedisFuture[0]));
      
            if(result)
                this.returnConnectiontoPool(connection);
        }


    }

However the system is not putting data in cache, when used with

  asyncCommands.setAutoFlushCommands(false);
  asyncCommands.flushCommands();

But, if it is used with regular set command without using

autoflush

then system puts the data in cache. I am wondering if there is a bug for using autoflush with async setup?

[jigneshmpatel]

also wondering if I use mset, then how much the performance different.