Dear Konrad, Thanks for your answer, our Actors didn't do anything that blocks the system. One possible cause for our performance problem is that in our "cluster-metrics-adaptive-group" router have just one routees associated to one actor (We have one actor for microsistem right now). We think to increase the number of actor for each microsistem and consequencialy the routees lists, is this a possible solution? If it is right to do so, there is a way to increase and decrease the group without going directly inside the code, and leaves akka do so ? Thanks Silvio
Il giorno lunedì 5 settembre 2016 11:26:58 UTC+2, Konrad Malawski ha scritto: > > 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 blocking in > your actors you'll end up blocking the entire system - this could be one of > the reasons you're seeing bad perf and no parallelism. > Another reason could be that you do all inside one actor or synchronously > in a thread, creating a bottleneck. > > Please explain a bit more on your setup and we could provide some more > helpful hints. > > Please also refer to the documentation when in doubt :) > > -- > Konrad `ktoso` Malawski > Akka <http://akka.io> @ Lightbend <http://lightbend.com> > > On 5 September 2016 at 11:22:26, silvio poma (silvio...@gmail.com > <javascript:>) wrote: > > 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 microservice > that receive a message from the client via HTTP and this message triggers > all the actors that start to send message one to each others. > We've created an Akka-Cluster and each microservice is a node of the > cluster. Every Actor send a message to a Router > (cluster-metrics-adaptive-group) that has his routees.paths that points to > the specific node. > Testing the performances of our system we realize that everything is too > slow and there is not any multithreading. > How does multithreading work? Is our infrastructure too complex? Is there > any best-practice we can implement to improve our system? > Thanks all! > Silvio > > -- > >>>>>>>>>> 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 akka-user+...@googlegroups.com <javascript:>. > To post to this group, send email to akka...@googlegroups.com > <javascript:>. > Visit this group at https://groups.google.com/group/akka-user. > For more options, visit https://groups.google.com/d/optout. > > -- >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
