maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Heinz Marbaise (JIRA)" <>
Subject [jira] [Commented] (MNG-6311) Maven intolerably slow when import scope used heavily in large project
Date Mon, 03 Sep 2018 15:51:00 GMT


Karl Heinz Marbaise commented on MNG-6311:

I meant to really test the current master of Maven Core which can be downloaded here: really see what the state of the current master is...and have a comparison between current
master and the fix branch ....

> Maven intolerably slow when import scope used heavily in large project
> ----------------------------------------------------------------------
>                 Key: MNG-6311
>                 URL:
>             Project: Maven
>          Issue Type: Bug
>          Components: core, Performance
>    Affects Versions: 3.5.0, 3.5.2
>            Reporter: David Churcher
>            Priority: Major
>              Labels: performance
>         Attachments: Call-tree-–-All-threads-together.html,,
> 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 
> 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

View raw message