-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Properly report Vertx worker pool size #35483
Conversation
This comment has been minimized.
This comment has been minimized.
0ffe08f
to
3eb83d8
Compare
cc @ahus1 |
This comment has been minimized.
This comment has been minimized.
Something seems to be wrong with the devmode tests. I'll have a look tomorrow. |
This comment has been minimized.
This comment has been minimized.
This is done by setting the relevant property in VertxOptions to the size of the Quarkus ExecutorService that is actually by Vertx (in prod mode). The reason we update VertOptions is that PoolMetrics uses it to calculate the blocking pool size. Closes: quarkusio#34998
Thank you @geoand - I only managed to test this today. I built your branch, and created a small demo application. With the default of max threads Although the threads will be started on-demand in the executor and are not really idle, those metrics make sense from the Vert.x facade. LGTM - thank you for this change! |
🙏 |
This is done by setting the relevant property
in
VertxOptions
to the size of the QuarkusExecutorService that is actually by Vertx
(in prod mode).
The reason we update
VertxOptions
is thatPoolMetrics
uses it to calculate the blockingpool size.
Closes: #34998