Classic Reactor pattern has very few context switches. Multithreaded implementations of this pattern also exists (Vert.x, for example).
Thanks for the link, I'll take a look deeper, but at first look seems issues described there are mostly related to particular Scala implementations.
As for performance benchmarking. There is well established benchmark - techempower.com/benchmarks/ . Simplest approach is to implement fiber-based version of this benchmark. There are several other implementations available, so it shouldn't be hard to implement another one.
Implementations which utilize asynchronous processing are already present in benchmark and usually are at the top of the list. Note, that this is not so for Akka-based implementation which suggests that something is wrong with either particular implementation or with Akka itself.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Classic Reactor pattern has very few context switches. Multithreaded implementations of this pattern also exists (Vert.x, for example).
Thanks for the link, I'll take a look deeper, but at first look seems issues described there are mostly related to particular Scala implementations.
As for performance benchmarking. There is well established benchmark - techempower.com/benchmarks/ . Simplest approach is to implement fiber-based version of this benchmark. There are several other implementations available, so it shouldn't be hard to implement another one.
Implementations which utilize asynchronous processing are already present in benchmark and usually are at the top of the list. Note, that this is not so for Akka-based implementation which suggests that something is wrong with either particular implementation or with Akka itself.