LIVE-4538 Restrict JVM tiered compilation level to 1 for harvester #752
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
waisingyiu
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this change?
We have experimented with the JVM settings about tiered compilation level in #756. The test results suggest that restricting the tiered compilation level to 1 is likely to improve the overall duration of harvester lambda.
This PR applies this JVM setting to the harvester lambda function via an environment variable.
How to test
This PR does not change any business logics.
We ran performance tests on
CODEto evaluate the impact of this JVM setting.How can we measure success?
We measure success using the 90in2min indicator, which is the percentage of recipients who are able to receive the notification under 2 mins.
Have we considered potential risks?
It may give poorer performance as the configuration and the workload are different in
PRODfromCODE, but there is no evidence to indicate so.In any events, we can revert this PR to restore to the original settings.