That's ok. I think I'll try the batching pattern (with max size and max
latency constraints) described in
https://groups.google.com/forum/#!topic/akka-user/todrna9GRS8/discussion
It seems to improve throughput substantially - in a quick test over a
simulated high latency link.
--
>>
Hi James,
Spray sits on top of akka.io. Unfortunately I don't think you can modify
how it talks to the Tcp connection. Anyway, since akka-http will use
reactive streams this batching behavior will be used by default. I am not
sure how much it will buy though, spray is already pretty fast.
-Endre
Thanks, that looks useful.
I'm using spray.client at the moment to make the network call (to a
web-service). I'm not sure how the akka.io stuff would fit in to this
though?
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs
Hi James,
You can achieve something similar with akka.io (
http://doc.akka.io/docs/akka/2.3.2/scala/io.html). For example, while your
actor waits from an Ack from a corresponding Tcp connection actor, it can
batch up the all the incoming ByteStrings and send them off in one piece
resulting in one
Hi All,
Has anyone used Akka to implement something akin to the 'Smart Batching'
pattern that Martin Thompson describes in this blog post?
http://mechanical-sympathy.blogspot.co.uk/2011/10/smart-batching.html
I've seen this
topic: https://groups.google.com/forum/#!topic/akka-user/todrna9GRS8/d
