Improve the startup time: skip test plan UI initialization #573
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
|
Hi @vlsi , Thanks |
@pmouawad , it was 2-3 seconds (before fix), and now it is 0.1sec (after fix) |
JMeter used to initialize all the components at the startup even in case the element was never used. This commit adds a shortcut for the well-known in-core components. User-visible outcome is the spashscreen no longer gets stuck for 2 seconds at 100%
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.
On my machine menu initialization takes 2-3 seconds (2.6GHz, SSD, fully cached).
Most of the cases the time is spent in creating Swing components, however, that work is not needed to get the label for the menu.
Even though the proper approach would be to split metadata from the UI components, I think it is fine to have an intermediate solution.
Note:
TestBeanGuidoes not initialize UI elements, however, full bean metadata initialization still takes time (e.g. JSR223 elements query ScriptEngine for the list of available languages)