soumyasd

@etaty thanks for your response. I'm trying to isolate this now. Can you tell me how you replaced akka-io with xnio ? I've also asked help from the Akka folks....

@etaty - the Akka team thinks its the lack of backpressure in the Akka client. That is the client is being flooded with so many requests that it cannot handle...

Sure. https://groups.google.com/forum/#!topic/akka-user/NrSkEwMrS3s I think this use case even though it not that common needs to be addressed in one way or the other. Hopefully we can find a good resolution...

@etaty - I've put an update to this on the Akka thread in case you want to have a look at it. https://groups.google.com/forum/#!topic/akka-user/NrSkEwMrS3s

@etaty thanks for reverting back. How is sending to the DummyRedisClient different from sending it to the RedisClient ? The GC pressure is high (at least for young generation (Edge...

I did post an update on the Akka thread. Looks like I was not applying the back pressure correctly. Now I can get much better performance compared to my initial...

@etaty - thank you for responding. I like Rediscala and would like to figure out a way around this limitation. I've create a gist here. https://gist.github.com/soumyasd/ac5b1d5f2ec3af21ace8 I've also updated some...

@etaty - is the TCP NO_DELAY setting for Rediscala configurable ? I think it's waiting for each Future to complete before sending the next one.

@etaty - is there a way to batch multiple Redis Operations using the RedisClient ?

Here is another chart for 1 million messages of 10K each. So support for batch mode will greatly increase the throughput and also reduce the latency. Let me know what...