-
Notifications
You must be signed in to change notification settings - Fork 351
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
JerseyCompletionStageRxInvoker should use AsyncInvoker #4255
Comments
If this is solved on the API level, it would possibly be done by a new method, and I am not sure what version of the API it should be in. So currently, it looks like this ought to be solved on the Jersey level. |
is possibly the simplest way to deal with it: basically Alternatively,
(plus replace all |
rx_invoker.zip |
How about #4283 ? |
To me using So I am looking for changing what |
While the API is designed to work with I have provided a PR #4283 with |
Expected: configure asynchronous thread pool the size of CPU count, be able to saturate CPU with long-running requests to other services.
Actual: CPU mostly idle.
RxInvoker
usesSyncInvoker
, and Jersey Client does the straightforward thing, which consumes the threads waiting for response.If JAX-RS API issue 703 is addressed at the API level, so much the better. If that issue is not fixed, at least we probably can assume that
AbstractRxInvoker.getSyncInvoker
returns the sameSyncInvoker
thatJerseyCompletionStageRxInvoker
passed to it in the constructor.A prototype fix with such type cast demonstrates the thread utilisation can become as Expected.
The text was updated successfully, but these errors were encountered: