if not then, oh well...
front-end API just needed to acknowledge that we had received them
didn't need to acknowledge if we had finished post-processing
that’s precisely the problem I’m also trying to solve
:)
currently working on making it easy to do this stuff with the clustering module on top of Akka.Remote :p
this is basically the reason why I turned to Akka.NET is to get millions of messages that go through our analytics system. So I’ll probably well be looking for advice sometime soon
:)
at peak loads I did about 20 million remote messages per day per Akka.Remote node (on the receiving end)
overhead was super minimal - like 3-15% CPU utilization on a medium-sized box on EC2
for that workload even at peak hours
your mileage may vary :p
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
what I'd like to do ideally is add a benchmarking system for Akka.Cluster
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