-
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
Fixes #12154 - Limit concurrent virtual threads. #12155
Fixes #12154 - Limit concurrent virtual threads. #12155
Conversation
Updated VirtualThreadPool to limit the number of concurrent virtual threads using a Semaphore. Updated modules and documentation. Signed-off-by: Simone Bordet <[email protected]>
@sbordet can we make this do if anybody configures the limit to less than 10000 it does "warning: just use normal threads. The emperor is indeed naked!" |
@gregw sure, but I think you meant "less than a million" 🤣 |
#jetty.threadPool.namePrefix=vtp<hashCode> | ||
|
||
## Maximum number of concurrent virtual threads. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think "concurrent" is correct or necessary here. It makes it sound like there could be a lot more virtual threads, but only a limited number concurrently executing (which is a factor of cores and/or native threads).
## Maximum number of concurrent virtual threads. | |
## Maximum number of live virtual threads. |
jetty-core/jetty-server/src/main/config/modules/threadpool-all-virtual.mod
Show resolved
Hide resolved
Signed-off-by: Simone Bordet <[email protected]>
Signed-off-by: Simone Bordet <[email protected]>
Updated VirtualThreadPool to limit the number of concurrent virtual threads using a Semaphore. Updated modules and documentation. Signed-off-by: Simone Bordet <[email protected]>
Updated VirtualThreadPool to limit the number of concurrent virtual threads using a Semaphore.
Updated modules and documentation.