[ https://issues.apache.org/jira/browse/MNG-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16314946#comment-16314946 ]
Karl Heinz Marbaise edited comment on MNG-6311 at 1/6/18 10:06 PM: ------------------------------------------------------------------- Can you give more details about the project ? Maybe an example setup how the project looks like so we might create a script generate a larger test project to see and measure things ? BTW. How much memory have you given? Are you running inside Jenkins / Pipeline ? was (Author: khmarbaise): Can you give more details about the project ? Maybe an example setup how the project looks like so we might create a script generate a larger test project to see and measure things ? > Maven intolerably slow when import scope used heavily in large project > ---------------------------------------------------------------------- > > Key: MNG-6311 > URL: https://issues.apache.org/jira/browse/MNG-6311 > Project: Maven > Issue Type: Bug > Components: core, Performance > Affects Versions: 3.5.0, 3.5.2 > Reporter: David Churcher > Labels: performance > Attachments: modelcachefix.diff > > > I have a build performance problem that is identical to MNG-5312, and has > appeared since MNG-6030 in Maven v3.5.0 reversed the patch for MNG-5312, > removing the ModelCache from some of the overloads for > DefaultProjectBuilder.build. > As in MNG-5312 the problem is in a large proprietary project. It uses up to 8 > levels of parent POMs, many of which use the import scope and have large > dependency-management sections, and has hundreds of dependencies that also > use the same parent POM hierarchy. Adding some logging shows that Maven does > over 800,000 uncached reads of parent POM files, which takes about half an > hour. With model caching this goes down to a few seconds. > I've attached a patch that fixes this by using a class-level ModelCache in > DefaultProjectBuilder. This does not suffer from the memory usage problems > reported in MNG-6030. -- This message was sent by Atlassian JIRA (v6.4.14#64029)