And newest Akka Kryo doesn't require pool-size as that's a java.util.ConcurrentLinkedQueue by default. I contributed that new mechanism to use ConcurrentLinkedQueue for the pool or your own implementation (See KryoQueueBuilder example in their doc).
On Monday, September 5, 2016 at 10:22:28 AM UTC+1, silvio poma 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+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.
