Hi,
Akka cannot control how the messages get chunked by the kernel to the wire.
I think though that if you turn off the socket option TcpNoDelay (it is on
by default in akka) then it enables Nagle's algorithm and the kernel might
send larger chunks.
-Endre
On Sat, May 30, 2015 at 10:20 AM, Laxma
Thank you for the response.
The payload is usually around 150MB. The network bandwidth is 1 Gbps. I am
thinking that larger chunk sizes would result in a better throughput.
I have set the value akka.io.tcp.direct-buffer-size to 64 MiB, but it
didn't change anything. So does it mean that OS is
Friday evening syndrome struck me it seems:
I missed the fact that you're talking about Akka IO, and not cluster
messages.
For that case 7KB indeed is not much. Are you sure the messages Write
messages
you issue should be causing larger chunks to be written?
The setting responsible for the size o
Hi Laxman,
I'd actually say that a 7KB message is not very small, sounds like a normal
sized message (you're probably using java serialization?).
I'd rather recommend using a better serializer, like protobuf, or kryo etc
in order to get the message size lower than worrying about tcp chunk sizes,
un
Hi,
I am using Akka-Cluster and sending large objects over network using Akka
IO through Tcp. The data is being cut down into very small chunks. The size
of the data ByteString received through 'Received' message is very small
(around 7KB). Is there any configuration setting using which I can s
