Memory footprint optimization and performance improvement #3118
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.
Team,
We observed high memory usage of configuration object on heavy mybatis applications. We observed that, we are repeatedly parsing the same XNodes and creating SQL nodes, instead of reusing the previously created SQLNode for the Xnode.
These changes holds the sqlNodeMap which consists of Xnode String(query String) as key, and respective SQLNode as value. So that, whenver we came across the same Xnode reference, we will use the previously created object from Map. This reduces the overall SQLNode Objects, and memory foot print of Configuration object.
These changes are already tested and validated in our project for more 12months.
With this change, My application memory dropped from 1.2GB to 350MB.