-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Review number of acceptor threads #11432
Comments
Defaulted to 1. Signed-off-by: Simone Bordet <[email protected]>
hello ,about selectors should be set? |
@zhipengzuo can you clarify your question? |
|
@zhipengzuo you typically want more than 1 selector if you want high throughput. Thus I would leave this at -1 to let the heuristic pick a value for you. |
thanks. |
Defaulted to 1. Signed-off-by: Simone Bordet <[email protected]>
Jetty version(s)
12+
Description
As reported in #11421, people can get confused by multiple acceptor threads competing for the blocking
accept()
call.A suggestion is that the heuristic should default to 1, or even to 0 (i.e. the accepts will be non-blocking).
The text was updated successfully, but these errors were encountered: