Hi Patrik, Thanks for your prompt response!
> Be aware of that the network roundtrips might dominate when you test with > empty work in a way that might not be relevant when the workers do real > work. > Right, I realize that, but I just wanted to get some baseline timing information for the absolute minimum amount of time needed to run X (empty) jobs. I guess I was just trying to measure the overhead of the system. I could simulate work taking some (fixed) time by inserting a (i know, bad!) Thread.sleep in the executor... I suppose that might make the system more fluent since the network will become less congested. I'll try that and see what effect it has... >> For those interested the actual code is here: >> https://github.com/borice/akka-grid-workers >> > > I noticed one error when use onSuccess callback. See here > http://doc.akka.io/docs/akka/2.3.0/general/jmm.html#Actors_and_shared_mutable_state > > Thank you, fixed. Given the way messages were exchanged I didn't think that was a problem, but I was just being lazy... :) > long garbage collection pauses can also trigger failure detection > That makes sense... > > >> >> I wonder whether the akka cluster extension in this case could be playing >> a part in the issues I'm seeing. The heartbeats or gossip messages >> exchanged between the cluster nodes might add unneeded traffic to a >> potentially-already-saturated network. I think that the simple solution I >> presented above could be implemented without using the cluster extension, >> by just using remote actors. The Producer only needs to know about the >> Coordinator (and monitor its lifecycle), and similar for the Workers. I >> wonder what the practical limits are for the maximum size of an akka >> cluster, assuming there are no JVM-related limits, when the only limit >> becomes the communication protocol/medium... >> > > > http://typesafe.com/blog/running-a-2400-akka-nodes-cluster-on-google-compute-engine<http://www.google.com/url?q=http%3A%2F%2Ftypesafe.com%2Fblog%2Frunning-a-2400-akka-nodes-cluster-on-google-compute-engine&sa=D&sntz=1&usg=AFQjCNE7AOab4aK84Q3vwCpYoGm47VuzzQ> > Very cool! I'll try to use some of the same tuning adjustments to the configuration settings that were described in that article. They will likely alleviate some of the issues I'm seeing... I'll see if I'll be able to run some tests across a > 2400 node akka cluster... if I do, I'll write about it here. Thanks again! Scala + Akka is an absolute pleasure to work with... -Boris -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
