Deserializer's performance problem - Githubissues

debasishg / scala-redis-nb

Implementation of a non blocking Redis client in Scala using Akka IO

204 stars 38 forks source link

Deserializer's performance problem #104

Open okumin opened 10 years ago

okumin commented 10 years ago

Some operation in ResponseHandling is not efficient and those may become bottlenecks when too many command is requested.

I found following bad operations.

Queue operation
RawReply#remaining() for every command response(maybe lead to array copy)
- https://github.com/debasishg/scala-redis-nb/blob/master/src/main/scala/com/redis/serialization/Deserializer.scala#L19
- https://github.com/debasishg/scala-redis-nb/blob/master/src/main/scala/com/redis/serialization/RawReplyParser.scala#L149