Several question about Redisson / Jedis

[mathieucarbou]

Note: I don't really know if there is a better place to ask for these sorts of questions... ;-)

Besides all the cool features added to Redisson to use locks, queues, maps, etc... How does Redisson performs compared to Jedis in terms of:

• memory usage
• speed
• number of concurrent connections supported
• use in multi-threading app requiring in both case using a pool
• thread-safety
• etc...

For having used both, I strongly prefer the api of Redisson (using publish subscribe in a reliable way with Jedis is a pain, and also there is no codec). But I am wondering, since their implementation only rely on simple sockets and a pool, how it compares to Redisson, which is based on Netty.

Also concerning thread-safety, having already aked a question about it, and in both libraries a connection pool is used for each operation and it is better to do so. So does thread-safety on a connection level really used ?

Thanks!

[mrniko]

In Redisson we don't need thread-safety on Connection because each connection can be used by single thread at one moment.

Also, all objects created by Redisson are fully thread-safe including Redisson."getAnyObject" methods.