Re: [akka-user] Akka Multithreading on Akka-Cluster

The Artery config is not correct, see release announcement for M4 /Patr ons 14 sep. 2016 kl. 14:12 skrev Guido Medina : > Hi Silvio, > > The following are the only things I can recommend you: > >- You have a short time to deliver? Why bother now with Artery if >that's

Re: [akka-user] Akka Multithreading on Akka-Cluster

Hi Silvio, The following are the only things I can recommend you: - You have a short time to deliver? Why bother now with Artery if that's the least of your problems? Your performance issue has nothing to do with Akka Cluster or Akka Remote. - Why use a future? Your future is

Re: [akka-user] Akka Multithreading on Akka-Cluster

Hi Guido, Following the release notes i create a config file like this: "remote": { "adapters": { "gremlin": "akka.remote.transport.FailureInjectorProvider", "trttl": "akka.remote.transport.ThrottlerProvider" }, "artery": { "bind-hostname": "127.0.1.1", "enabled": "on", "hostname":

Re: [akka-user] Akka Multithreading on Akka-Cluster

What you have seen for Akka Artery M4 is what is available at the moment, I did test it when it was M2 but I haven't done anything with M4 yet, for M4 I imagine the same applies as it was for M4, the release notes is the guide. Have you measured your application like you were suggested? I

Re: [akka-user] Akka Multithreading on Akka-Cluster

Hi Guido, can you suggest me some guide that explains the configuration changes that need to be done? I've seen that with the M4 it was included the configuration for for usage with Docker, that is what i need. Thanks Silvio Il giorno mercoledì 7 settembre 2016 17:50:44 UTC+2, Guido Medina ha

Re: [akka-user] Akka Multithreading on Akka-Cluster

I have an http endpoint with a consumerActor (in Node 0) that read the msg from the camel msg and with it create our Message.class than it send to a router1 that forward to one of "N" Worker1 in Node 1, Worker1 make a query on Couchbase process the result and send the Message.class to to a

Re: [akka-user] Akka Multithreading on Akka-Cluster

What is your bottleneck? On Tue, Sep 13, 2016 at 10:13 AM, silvio poma wrote: > Thanks guy, I eventually fixed all the configuration as you suggested and > now everything is working. > I can see a big improvement in the average time of response of my service > but the

Re: [akka-user] Akka Multithreading on Akka-Cluster

Thanks guy, I eventually fixed all the configuration as you suggested and now everything is working. I can see a big improvement in the average time of response of my service but the throughput is still the same of before. Any other suggestions, my target is to have throughput as high as

Re: [akka-user] Akka Multithreading on Akka-Cluster

Your contribution makes ID strategy automatic even better, you know automatic = explicit + incremental right? So I think it would also work for your project, but I do understand why you have chosen explicit as you want to fail if you introduce a new class and forget to register it. I use

Re: [akka-user] Akka Multithreading on Akka-Cluster

On Fri, Sep 9, 2016 at 2:51 PM, Guido Medina wrote: > The problem with explicit is that there are so many "trait" and "classes" > not really registered which is why I use it, > it is the newest ID strategy as it register things you might not care but > commonly used messages

Re: [akka-user] Akka Multithreading on Akka-Cluster

The problem with explicit is that there are so many "trait" and "classes" not really registered which is why I use it, it is the newest ID strategy as it register things you might not care but commonly used messages you register, that way you get performance for what is important and automatic

Re: [akka-user] Akka Multithreading on Akka-Cluster

On Fri, Sep 9, 2016 at 12:27 PM, Guido Medina wrote: > Also, what ID strategy are you using? I see none configured so it it is > using the default, try setting it like I posted in the example which is > "automatic" > Yeah, this is what I was going to suggest. The default

Re: [akka-user] Akka Multithreading on Akka-Cluster

Also, what ID strategy are you using? I see none configured so it it is using the default, try setting it like I posted in the example which is "automatic" On Friday, September 9, 2016 at 5:26:00 PM UTC+1, Guido Medina wrote: > > Are you sharing the same conf file? if you registered classes

Re: [akka-user] Akka Multithreading on Akka-Cluster

Are you sharing the same conf file? if you registered classes then all nodes must share the same Kryo config. On Friday, September 9, 2016 at 3:44:38 PM UTC+1, silvio poma wrote: > > Just to be clear, my class: com.test.common.LoginRequest is formed of 4 > strings and an actorRef > Thanks all

Re: [akka-user] Akka Multithreading on Akka-Cluster

Just to be clear, my class: com.test.common.LoginRequest is formed of 4 strings and an actorRef Thanks all 2016-09-09 16:34 GMT+02:00 silvio poma : > Right now one of the biggest and strange problem is that when arrive a > message from the Actor A in the node 1 to the

Re: [akka-user] Akka Multithreading on Akka-Cluster

Right now one of the biggest and strange problem is that when arrive a message from the Actor A in the node 1 to the actor B in the node 2 the node 2 is immediately disassociated from the cluster. The message that the actor A sends to actor B is our custom class that we are serializing using

Re: [akka-user] Akka Multithreading on Akka-Cluster

What problems are you facing? I'm in my second project with Java 8 + Akka so maybe I can help. To integrate the akka-kryo extension all you need is the dependency and few lines at the configuration you are using, no code changes are needed, here is an example: akka { // Log4j2 extension

Re: [akka-user] Akka Multithreading on Akka-Cluster

Hi Guys, Thanks a lot everybody. Yours tips were very useful and we are working on it. We've already improved the router and the disptachers configuration achieving very good results. Now we are trying to leave the java serialization and pass to another one more efficient, but we are having

Re: [akka-user] Akka Multithreading on Akka-Cluster

Hi Guys, Thanks a lot everybody. Your tips were very useful and we are working on it. We've already improved the router and the disptachers configuration achieving very good results. Now we are trying to leave the java serialization and pass to another one more efficient, but we are having some

Re: [akka-user] Akka Multithreading on Akka-Cluster

Artery is at in milestone 3 (m3), you are welcome to use as I believe it is in an extremely good shape but I would pursue both, as it will only require you a day of work (as a newbie) in configuration and dependencies, no code changes will be required:

Re: [akka-user] Akka Multithreading on Akka-Cluster

IMO Artery won't help much if using Java Serialization. Java Serialization is notoriously slow. On Wed, Sep 7, 2016 at 5:50 PM, Guido Medina wrote: > Artery is at in milestone 3 (m3), you are welcome to use as I believe it > is in an extremely good shape but I would pursue

Re: [akka-user] Akka Multithreading on Akka-Cluster

Dear Guido, Thanks a lot for you answer. We have already improved our concurrency model, using multiple instances for each actor, that now work in parallel using multiple dispatcher. Now we have not so much time to release our product to the client. What do you suggest to focus our efforts on?

Re: [akka-user] Akka Multithreading on Akka-Cluster

Messages can be slow when being sent remotely from node A to node B, current Akka remote will give you a top of 100k msg/sec best scenario and that depending on the message size, there is a new Akka remote (Akka artery which is a rewrite of Akka remote) on the way so that shouldn't discourage

Re: [akka-user] Akka Multithreading on Akka-Cluster

This is not really enough information to say where or what the bottlenecks are. If you need a full architecture overview that's a commercial thing we can offer. Having that said, you did not mention what HTTP server you're using. Actors are simply multiplexed onto threads, so if you're doing

[akka-user] Akka Multithreading on Akka-Cluster

Hi All, Working on a project for a big client that want to switch from a monolithic infrastructure to a microservice one we are getting stuck in a big doubt. We are making an infrastructure where each microservice are deployed in a different container on an ECS instance, than we have the first