[jira] [Issue Comment Deleted] (MNG-6311) Maven intolerably slow when import scope used heavily in large project

["Karl Heinz Marbaise (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MNG-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Heinz Marbaise updated MNG-6311:
-------------------------------------
    Comment: was deleted

(was: I'm out of the office until 15 January 2018. For anything urgent please contact Jayson Elliott

PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL

If you receive this message by mistake, please notify the sender at IAG New Zealand Limited
immediately and destroy the message.  This message and any attachments may be confidential or
privileged.  You may be liable if you use or retain this information without IAG NZ's permission. 
Any information that does not relate to IAG NZ's official business is not given or endorsed by IAG
NZ.  Thank you.
)

> 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)