V
V
Also another piece to look at, is akka-io the buffers and osx buffers. Because maybe once they are all full they might start to be slow.
Hey thanks for your work. Could you publish the code in gist (or a repo if you prefer), so other can help you ? In the first graph, the write...
You can do a batch with a Transaction message https://github.com/etaty/rediscala/blob/ab29ee24b024b8dced58f618d6a32bb91ba91bf2/src/main/scala/redis/actors/RedisClientActor.scala#L28 A transaction contains a sequence of Operations https://github.com/etaty/rediscala/blob/ab29ee24b024b8dced58f618d6a32bb91ba91bf2/src/main/scala/redis/Operation.scala#L31 it is used to emulate Redis transaction
I am using the Nagle algo in rediscala (so i am waiting for the ack of a socket write before sending the next write). It limits the number of messages...
just get or ping (small message)
Use a builder returning a Future[]
Quick response, not in 2 weeks. There is a SBT option to not check SNAPSHOT every single time. (something related to offline also)
yes there is no throttling in the redis protocol. Only way is to send a batch and wait for the Futures complete state, and send another batch.
I have not played with it, but there is bounded queue in akka, if you are able to tell the RedisActor to use a bounded queue.
Hum wait that doesn't work (The redis actor always consume and add to a queue the rediscommands). Only way is to listen for the redis response and send more.