-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Use Virtual Threads when applicable #25855
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
base: master
Are you sure you want to change the base?
Conversation
Any measurable benefits? Data please :) |
@losipiuk it's hard to quantify - this will use less resources but we do not track threads in the memory accounting |
@@ -109,7 +108,7 @@ public void setup(Binder binder) | |||
|
|||
newOptionalBinder(binder, Key.get(ExecutorService.class, ForJdbcClient.class)) | |||
.setDefault() | |||
.toInstance(newCachedThreadPool(daemonThreadsNamed(format("%s-jdbc-client-%%d", catalogName)))); | |||
.toInstance(newThreadPerTaskExecutor(virtualThreadsNamed(catalogName + "-jdbc-client-#%s"))); |
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.
nit:
format("%s-jdbc-client-#%s", catalogName)
Started benchmark workflow for this PR with test type =
|
This is mostly I/O intensive (reading JARs)
bcbeae0
to
0678d52
Compare
Description
Additional context and related issues
Release notes
( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text: