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
8273972: Multi-core choke point in CMM engine (LCMSTransform.doTransform) #5671
Conversation
|
* @test | ||
* @bug 8273972 | ||
* @summary Verifies that ColorConvertOp works fine if shared between threads | ||
* @run main/othervm/timeout=600 MTTransformValidation |
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.
600 is quite pessimistic, on my system both tests are executed around 1 minute, but I am not sure how it will execute on the slow mac mini, so increased the timeout.
This looks OK but I want to submit a test job to make sure no nasty surprises |
@mrserb This change now passes all automated pre-integration checks. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 25 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.
|
/integrate |
Going to push as commit e49e5b5.
Your commit was automatically rebased without conflicts. |
Initially, the bug was discussed here:
https://stackoverflow.com/questions/35264582/why-is-multithreading-slowing-down/35264813
The root cause is that if for some reason directly or indirectly the color transform object is shared across the threads it cannot be used for parallel color transformation because the method LCMSTransform.doTransform() is synchronized.
This code seems to be created when the littlecms 1.x was used which was not thread-safe, but the latest version is thread safe (subject to bugs). I can check that by compiling lcms with #define CMS_NO_PTHREADS which will cause some of our tests fail here and there.
To check that transform can be used across the threads I created two quite heavyweight tests which tests different color transformations using different threads.
The fix moves the data for the native transform from the LCMSTransform object to the NativeTransform class just to simplify synchronization steps, so only one volatile read of "transform" is executed in the common path.
Result for the testcase attached to SO: https://stackoverflow.com/a/35264713
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5671/head:pull/5671
$ git checkout pull/5671
Update a local copy of the PR:
$ git checkout pull/5671
$ git pull https://git.openjdk.java.net/jdk pull/5671/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5671
View PR using the GUI difftool:
$ git pr show -t 5671
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5671.diff