Xiong Luyao created MNG-7509:
--------------------------------
Summary: Huge memory cost when parent pom widely used in a big
project for dependencyManagement
Key: MNG-7509
URL: https://issues.apache.org/jira/browse/MNG-7509
Project: Maven
Issue Type: Improvement
Components: Performance
Reporter: Xiong Luyao
Attachments: image-2022-07-09-09-37-53-823.png,
image-2022-07-09-09-38-26-354.png
When maven try to resolve dependency relationship, it will create many objects
of dependency / artifact. Even the dependency/artifact content is totally same,
but just in different models. It cost huge memory if there is a big
dependencyManagement parent pom in each dependencies of the project.
Here is a real case. As below picture, there is over 3000 business domain
libraries, each library may rely on several other libraries among them. So the
library which didn’t rely on each other will be built first and the library
only relies on the built libraries will be built, until all the libraries have
been built. In this way, we use a parent pom to maintain the version of these
3000+ libraries version and make each library introduce it. So that it can keep
all the libraries are built from same base.
But it costs huge memory in above ways to built libraries. And even the
libraries have been released, if the project which contains a lot of above
libraries, it also cost huge memory when building project.
!image-2022-07-09-09-37-53-823.png|width=493,height=226!
Here is a thread dump when building a real project with above libraries. The
top 5 objects are all related to org.eclipse.aether.graph.Dependency.
!image-2022-07-09-09-38-26-354.png|width=510,height=199!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
