Re: [akka-user] Use of high performance bounded mail box.

The Gist example is actually a "bounded *logger* mailbox for Akka", basically the Akka logger is an actor, with such config you are basically replacing the mailbox of such logging actor for a bounded MPSC mailbox queue. On Wed, Jul 26, 2017 at 9:18 PM, Guido Medina wrote: > I

Re: [akka-user] Use of high performance bounded mail box.

I use high performance bounded queues in my Akka projects, I used to use the ones from JCtools but I discovered that Agrona which Aeron depends on (which Akka Artery depends on) have similar implementations, anyway, linking stuff: - *Agrona:*

Re: [akka-user] Use of high performance bounded mail box.

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,

Re: [akka-user] Use of high performance bounded mail box.

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

[akka-user] Use of high performance bounded mail box.

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