It looks like the asynchronous interface to debasishg/scala-redis is synchronous under the hood, using a pool of blocking connections. This means that there is

It looks like the asynchronous interface to debasishg/scala-redis is synchronous under the hood, using a pool of blocking connections. This means that there is no pipelining. Each of these blocking connections must wait for a request to travel over the wire, be handled by redis, and travel back before it can be reused. An asynchronous client allows full pipelining automatically, which is a much more efficient use of a single connection. > we have noticed performance issues as redis serves only 1 req every time there was too much time spending in thread-join Performance should be better with an asynchronous client. When I've benchmarked e.g. jedis vs various async clients, that's been the case.