[akka-user] Re: Akka dispatchers are not reused instead new dispatchers are created overtime

2016-02-18 Thread Hareesh Jagannathan
We were able to solve this issue by changing my executors for those blocking actors. As a general pattern its better to do the following : 1. Finding actors behaviour/usage and identifying those service calling or IO performing actors. 2.Using thread pool executors instead of fork join pool exec

[akka-user] Re: Akka dispatchers are not reused instead new dispatchers are created overtime

2016-02-16 Thread Hareesh Jagannathan
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 s

Re: [akka-user] Re: Akka dispatchers are not reused instead new dispatchers are created overtime

2016-02-16 Thread Viktor Klang
No, I'd use a dedicated dispatcher for the routees which do IO, use ThreadPoolExecutor. -- Cheers, √ On Feb 16, 2016 5:24 PM, "Hareesh Jagannathan" wrote: > > I do have blocking file-io in one of the router of the pipeline. > > Should i used Pinned dispatcher for those and go ahead with what yo

Re: [akka-user] Re: Akka dispatchers are not reused instead new dispatchers are created overtime

2016-02-16 Thread Konrad Malawski
You may want to read my SO answer which explains what you're seeing somewhat (including pictures and how to configure dispatchers properly): stackoverflow.com/questions/34641861/akka-http-blocking-in-a-future-blocks-the-server/34645097#34645097 --  Cheers, Konrad 'ktoso’ Malawski Akka @ Typesafe

[akka-user] Re: Akka dispatchers are not reused instead new dispatchers are created overtime

2016-02-16 Thread Hareesh Jagannathan
I do have blocking file-io in one of the router of the pipeline. Should i used Pinned dispatcher for those and go ahead with what you suggested for non blocking actors? On Tuesday, February 16, 2016 at 9:33:17 AM UTC-6, Hareesh Jagannathan wrote: > > Akka application spins a lot of new dispat

Re: [akka-user] Re: Akka dispatchers are not reused instead new dispatchers are created overtime

2016-02-16 Thread Viktor Klang
If you don't do any blocking then your max should be the number of cores you have and the factor about 0.6-0.7 -- Cheers, √ On Feb 16, 2016 5:17 PM, "Hareesh Jagannathan" wrote: > See thats my problem. All i have is 8core CPU (3 nodes) so basically 24 > cores. > > I understood the below form

[akka-user] Re: Akka dispatchers are not reused instead new dispatchers are created overtime

2016-02-16 Thread Hareesh Jagannathan
See thats my problem. All i have is 8core CPU (3 nodes) so basically 24 cores. I understood the below form documentation and blogs. Max*factor is most number of threads i can have. Min*factor in minimum number of threads i can have. So what exactly would you recommend. also why is that i am

Re: [akka-user] Re: Akka dispatchers are not reused instead new dispatchers are created overtime

2016-02-16 Thread Viktor Klang
Wow, you have 500 CPU cores on your machine? -- Cheers, √ On Feb 16, 2016 5:01 PM, "Hareesh Jagannathan" wrote: > Thanks for responding quickly. Attaching a screeshot form visual Vm. As > you can see there are more than 700 dispatcher for one my system. > > My design is as below. > >1. The