I’m still studying the architecture for this project.. because right now (for this client in particular and with our database) the number of messages is just waay too inneficient…. 600M a day
its just feels like a waste of bandwidht if you ask me
I was going to say
I hope your EC2 sales rep / whatever vendor you use drives a nice car
These guys have their own machines/data center
although in-process messages within akka.net are dirt cheap from an overhead point of view
remote messages, less so - serialization overhead on both ends of the connection can add up
it did some remoting testing.. and firing 1M took the sender something 700ms...
but would like to
hmmm, actually
something like 250,000 reads per second on 2 threads at 3-4% CPU
never done anything like that for Akka.Remote though
test how different cluster sizes perform
and make it pluggable for people's apps
as for what you were saying @coffeeyesplease - I think the reason the recieving end is slower is because of how remote messages get delivered to their recipients
it's going to follow Netty's design much more closely than the current version
(Akka.Cluster will ship after Akka.NET 1.0 is released)
if it's a Helios issue then I know exactly where the problem is
it's the
LengthFrameDecoder
either it or the
ByteBuf sitting on top of it grabs only a partial chunk of a message
assumes the message is corrupt
and discards bytes until the buffer is empty