additional info:

scalaVersion = "2.11.6"

Akka      = "2.3.6"


The application logic is like:


Using spray as facade, creating 1 actor for each request, do some processing, 
hit an external resource with spray-can client and return the response.


Leon



在 2015年6月2日星期二 UTC-7上午1:57:41,Leon Ma写道:
>
> Hi, 
>
> My JMC profile indicates that ForkJoinPool.scan is the most hot method 
> under pressure:
>
> Method Sample Count Percentage(%)
> scala.concurrent.forkjoin.ForkJoinPool.scan(ForkJoinPool$WorkQueue) 1,031 
> 4.607
>
>
> Does it mean there're too many threads are trying to stealing work from 
> others?
>
> Currently I'm using below  config: (my box has 4 cores)
>
> akka.actor.default-dispatcher.fork-join-executor {
>
>   # Min number of threads to cap factor-based parallelism number to
>
>   parallelism-min = 2
>
>   # The parallelism factor is used to determine thread pool size using the
>
>   # following formula: ceil(available processors * factor). Resulting size
>
>   # is then bounded by the parallelism-min and parallelism-max values.
>
>   parallelism-factor = 0.75
>
>   # Max number of threads to cap factor-based parallelism number to
>
>   parallelism-max = 64
>
> }
>
>
>
> I tried small value for parallelism-factor, but it seems the scan call 
> still way too much.
>
>
> Any suggestions?
>
>
>
> Thanks
>
>
> Leon
>
>
>
>
>
>
>
>
>
>
>
>

-- 
>>>>>>>>>>      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 http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to