Skip to content
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

[Bug]: executeBlocking is executed with ordered=true by default #290

Open
1 task done
pk-work opened this issue Mar 21, 2023 · 0 comments
Open
1 task done

[Bug]: executeBlocking is executed with ordered=true by default #290

pk-work opened this issue Mar 21, 2023 · 0 comments
Labels
bug Something isn't working needs triage This issue needs to be investigated and confirmed as a valid

Comments

@pk-work
Copy link
Contributor

pk-work commented Mar 21, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Two years ago executeBlocking got a new default value: ordered = true [1]. We now saw in one of our Quarkus apps, that this has massive performance issues. So if ordered = false is possible, we should use it.

[1] eclipse-vertx/vert.x@87004b7

Expected Behavior

My suggestion is to modify AsyncHelper in a way, that ordered = false will be used, or is at least the default value.

Steps To Reproduce

No response

Environment

- OS:
- Java:
- NeonBee:

Relevant log output

No response

Anything else?

No response

@pk-work pk-work added bug Something isn't working needs triage This issue needs to be investigated and confirmed as a valid labels Mar 21, 2023
@pk-work pk-work changed the title [Bug]: [Bug]: executeBlocking is executed with ordered=true by default Mar 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage This issue needs to be investigated and confirmed as a valid
Projects
None yet
Development

No branches or pull requests

1 participant