Aaron Stannard

Can you test with the latest nightly to verify these are fixed? Sent from my iPhone > On Nov 26, 2021, at 8:25 AM, Andreas Dirnberger ***@***.***> wrote: > >...

As for the DotNetty CPU issues - can’t fix those without replacing the transport, which we are planning on doing but it’s a ways out. Sent from my iPhone >...

@markusschaber ah, my comment was for @Zetanova to resolve his startup issue with the `ChannelDispatcher`

The times I've tested that, there have been some throughput tradeoffs - but on balance that might be the better trade for your use case. In terms of replacing the...

> Thanks for your efforts. I'm looking forward to an official solution, which can be used in production code without bending compliance rules. :-) Naturally - if @Zetanova is up...

> As far as I can see, the main issue with the schedulers are the busy loops, things like Thread.Sleep(0) in tight loops seem to burn most of the CPU...

> Independently, one could argue that any starvation by using the normal thread pool is either a misconfiguration of the thread pool (not enough minimum threads), or a misuse of...

> I'm not sure whether busy waiting actually brings enough benefits, compared to just using a lock / SemaphoreSlim or similar primitives using the OS scheduler. (As far as I...

> As far as I can see, it should be possible to spawn several Akka actor systems as cluster members within the same process (as everything is nicely encapsulated, no...

> @Aaronontheweb The tradeoff is not between better idle-cpu and throughput but between idle-cpu and latency Reason is that a max used system (100% load) has 0% idling and should...