Good to know that typed actors are going to use bounded mail boxes. Just curious, don't people face issues in production systems because of unbounded mail boxes? Our performance tests on the logger were showing that once mail box accumulates lots of messages, it puts unreasonable load on memory, even after messages are consumed by the actors.
On Sat, Jul 15, 2017 at 2:18 PM, Konrad “ktoso” Malawski < konrad.malaw...@lightbend.com> wrote: > The current default, more than anything, is bound to be the default since > it was the default since the inception of Akka and going for a bounded one > by default now could make some users unhappy. > > Having that said, we're actively looking forward to pick a bounded impl > for Akka Typed. Then people come to it with new expectations and it's > easier for us to justify the change. > > We also have looked at a number of such impala, including benchmarks etc > and they're definitely very cool. > > So it's not that we don't want to, rather it is a question when we do :) > > On July 15, 2017 at 17:33:12, Unmesh Joshi (unmeshjo...@gmail.com) wrote: > >> Hi, >> >> We had some custom requirements for building a logging library wrapper >> for our project. The project includes multiple subsystems, each developing >> components which are essentially actors. All modules/actors are supposed to >> be using our logging interface. >> After some research, we found neopersist library (https://github.com/ >> nestorpersist/logging) which seems to fit our needs. One of the key >> aspects of this library is the use of LoggingActor which handles all the >> logging events. >> Conceptually, this should perform pretty well, and comparable to log4j >> async appender. >> We ran some performance tests similar to the ones for log4j 2 as >> described here https://logging.apache.org/log4j/2.x/performance.html. >> As we expected, the bottleneck was the unbounded mailbox for Actors. The >> performance tests with jmh were just too slow and throughput was too low >> after a few iterations. >> We changed our mailbox configuration to use NonBlockingBoundedMailbox, >> and performance then was comparable to AsyncAppender of log4j 2. >> Log4j2 AsyncAppender uses lmax disruptor. >> >> So the question is, why isn't some variant of bounded mail default in >> akka? >> Was there any thought/discussion happened to use lmax disruptor based >> mail box implementation? and why was it not done? >> >> Thanks, >> Unmesh >> >> -- >> >>>>>>>>>> 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. >> > -- >>>>>>>>>> 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.
