fs2-netty
fs2-netty copied to clipboard
Figure out why on earth RPS is so bad
Why does fs2-io beat fs2-netty so handily in the RPS benchmark? Is it just the difference between accept() vs read() with a set handler?
@vasilmkd proposed the following explanation here:
fs2-io can use all threads of the runtime to accept and service requests while I believe virtually all services have to be scheduled on the runtime through one thread
I think this is quite true. All threads can queue up read()s, but only one thread is available to actually read them. Just naively increasing the number of workers also doesn't really address this.