400 asks in 5 seconds should be nowhere near the number of asks/request-responses you can run through a single typed actor. Likely something in your logic or in how you measure is not quite right. As a reference, with a naive ping-pong test I can do around ~170 asks per ms on my machine.
Profiler showing the scheduler as cpu hotspot means your system isn't really doing anything. If you want more help, please share the complete microbenchmark. -- Johan Akka Team On Friday, August 25, 2017 at 10:09:46 AM UTC+2, Kostas kougios wrote: > > Did a quick test commenting out the blocking .awaitFor(). So there was no > blocking call. But still it is too slow. > -- >>>>>>>>>> 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.
