-
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
Remove the workaround for ForkJoin to spin up threads #5631
Comments
I'm not sure the commit has been included in 19.2.x: From what I can see, it's only in 19.3 but I might be wrong. |
This was included in 19.3.0 indeed. |
This would be a good fix to have, I think it may speed up our native builds as I know the native compilation does use fork join internally in places. |
@gwenneg Good to know. Any chance you could take this as part of your on going work with |
@machi1990 Sure, this could be part of #5358 |
Thanks @gwenneg |
Done in #5358. |
Describe the bug
We set
-J-Djava.util.concurrent.ForkJoinPool.common.parallelism=1
inNativeImageBuildStep
to workaround for
It seems the GraalVM issue was resolved; are we safe to remove the workaround from Quarkus?
@stuartwdouglas needs your opinion at least
The text was updated successfully, but these errors were encountered: