Hi All, We've implemented an online learning/recommendation system adopting 2 approaches: 1) Sync REST and learning components shielded with ReentrantReadWriteLock's 2) Sync REST and learning components deployed in Akka actors
Throughout our stress tests using JMeter and several above 500K real data, we analysed a huge set of configurations for Akka from connector impl(component between akka actors and REST service), actor architecture, dispatcher and mailbox settings perspectives. Till now, best performance obtained via harnessing dedicated distinct dispatchers with some (sub)optimized parameters for connector (fully future-based and/or router+actor+future/based) and core learning actors. In addition to this, using SingleConsumerOnlyUnboundedMailbox as default mailbox type brings some improvements. After extensive trials, comparing to ReentrantReadWriteLock-based approach, what we observe is recommendation service response time is always around 2 times more in Akka-based impls, although Akka-based impls might give slightly better throughput in some cases. My questions: 1) Considering response time, is Akka latency is inevitable comparing to classical lock-based impls on top of a REST service? Any general suggestion/guideline to improve response time in Akka REST service actors? 2) Shall we "really" expect a better throughput if we use Async REST? Thanks a lot. Regards, Cagri Yalcin -- >>>>>>>>>> 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.
