Thanks a lot all. I will go ahead rethink the usage of default dipatcher for few of my actor(service calling and file-io calling ). Think its wise to move a threadpool executor based dispatcher.
On Tuesday, February 16, 2016 at 9:33:17 AM UTC-6, Hareesh Jagannathan wrote: > > Akka application spins a lot of new dispatchers overtime instead of > reusing . The old dispatchers are going back to waiting state and never > been reused or terminated. > > We use akka's default dispatcher with fork-join executors. we do override > the default parallelism parameter between our actors based on actors > purpose. > > Is there a configuration that we are missing that causing this issue? > -- >>>>>>>>>> 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 https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
