Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out why on earth RPS is so bad #4

Open
djspiewak opened this issue Jan 24, 2021 · 1 comment
Open

Figure out why on earth RPS is so bad #4

djspiewak opened this issue Jan 24, 2021 · 1 comment

Comments

@djspiewak
Copy link
Member

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?

@djspiewak
Copy link
Member Author

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant