Option useHigherMethodCounts Now Correctly Sets the scount #7372
Conversation
TR_UseHigherUserCounts now sets the intial scount to the value of initial count after the initial count has been set, to avoid the initial scount being set to -1 Measurements: when running acmeairee8 with `-Xjit:useHigherMethodCounts -Xaot:useHigherMethodCounts`, there is a 2% throughput improvement with 2.3% start-up time increase Signed-off-by: Luke Li <luke.li@ibm.com>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Thank you for supporting the project, and congratulations on your first contribution! A project committer will shortly review your contribution. In the mean time, if you haven't had a chance please skim over the contribution guidelines which all pull requests must adhere to. If the ECA pull request check fails, have a look at the instructions for signing the ECA in the legal considerations section.
If you run into any problems our community will be happy to assist you in any way we can. There are a number of recommended ways to interact with the community. We encourage you to ask questions, or drop by to say hello.
|
@mpirvu could you please review? If the change looks good to you I can run tests/merge. |
|
Jenkins build all |
TR_UseHigherUserCounts now sets the intial scount to the value of initial count after the initial count has been set, to avoid the initial scount being set to -1
Measurements: when running acmeairee8 on OpenJ9 with
-Xjit:useHigherMethodCounts -Xaot:useHigherMethodCounts, there is a 2% throughput improvement with 2.3% start-up time increase