[akka-user] Re: Akka HTTP performance for short lived connections

2016-04-17 Thread Andrew Gaydenko
Adam, just curious, can you, please, supply some example ApacheBench output? -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search the archives:

Re: [akka-user] Akka HTTP performance for short lived connections

2016-04-17 Thread Adam
OK, thanks. So just to be certain - in the meantime, is it expected that I'll see Akka HTTP perform ~100 times worse (or let's just say "much worse") than Play framework for such cases? I was hoping it's actually something that I'm doing wrong because I was expecting it to be worse per the

Re: [akka-user] Akka Singleton Cluster: Knowing when standby master has become primary

2016-04-17 Thread Patrik Nordwall
Perhaps take a look at Cluster Singleton documentation: http://doc.akka.io/docs/akka/2.4.4/scala/cluster-singleton.html#cluster-singleton-scala /Patrik On Sun, Apr 17, 2016 at 7:01 PM, Prasanna Thirumalai wrote: > In a singleton cluster with 2 seed nodes, one of them is

Re: [akka-user] Akka Cluster: Why Member does not have name property?

2016-04-17 Thread Patrik Nordwall
The address contains the the name of the ActorSystem, but that is not in any way related to the actor that you mentioned earlier. The actor system name must be the same for all cluster nodes, so that is not what you are looking for. I'll read your other posts and try to understand what you want to

[akka-user] Akka Singleton Cluster: Knowing when standby master has become primary

2016-04-17 Thread Prasanna Thirumalai
In a singleton cluster with 2 seed nodes, one of them is primary master and other one is standby, what notification should I subscribe to in the standby master that informs it that it has been moved to primary? -- >> Read the docs: http://akka.io/docs/ >> Check the

Re: [akka-user] Akka Cluster: Why Member does not have name property?

2016-04-17 Thread Prasanna Thirumalai
Yes, I understand MemberUp is an event when a node comes up, but the MemberUp event contains Member attribute in it. (MemberUp(member)). Shouldn't that Member attribute in the MemberUp event contain the name of the node that came up in the cluster? On Sunday, April 17, 2016 at 3:58:46 AM

[akka-user] What config affects the number of threads for an ActorSystem?

2016-04-17 Thread Steve Rehrauer
I have an application that doesn't specify a custom dispatcher. We see the number of threads maxing out at 50, and would like to increase it. This doesn't seem to line up with any of the default config I see in Akka? I see

Re: [akka-user] Akka Cluster: Why Member does not have name property?

2016-04-17 Thread Patrik Nordwall
No, MemberUp is a notification that a node/ActorSystem was added to the cluster. You can read about ActorSystem here: http://doc.akka.io/docs/akka/2.4.4/general/actor-systems.html /Patrik lör 16 apr. 2016 kl. 21:48 skrev Prasanna Thirumalai : > I am sorry but I do not

Re: [akka-user] Re: akka-stream: How to define a Processor in Java

2016-04-17 Thread Johan Andrén
In general you should seldom have to write your own stages as there is a very rich set of built in stages provided. For example if you have a request-response you want to perform with an actor you can use mapAsync to interact with the actor from a stream. Something like this: val