I know this is a vague question and the answer is really 'it depends', we 
are in a situation where we need to give some predictions on CPU capacity 
needed by Akka HTTP services we are building, even before the application 
is built and any tests are run for predicting capacity. We are replacing 
existing application which is old application running spring services. So I 
have few questions.
1. Is there a rule of thumb based on previous observations which can help 
saying if a blocking IO web service needs 2 CPUs and 100 threads, Akka HTTP 
will probably need only 1 CPU and may be just few threads.
2. Is it fair to assume that non blocking Apps like Akka HTTP, will be more 
'heap heavy' and it will be good to have space CPU capacity for running 
parallel GC?


** New discussion forum: https://discuss.akka.io/ replacing akka-user 
google-group soon.
** This group will soon be put into read-only mode, and replaced by 
** More details: https://akka.io/blog/news/2018/03/13/discuss.akka.io-announced
>>>>>>>>>>      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.

Reply via email to