[
https://issues.apache.org/jira/browse/MNG-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069841#comment-17069841
]
Hudson commented on MNG-6633:
-----------------------------
Build failed in Jenkins: Maven TLP » maven-studies » maven-metrics #4
See
https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/4/
> ExcludesArtifactFilter is a memory hog
> --------------------------------------
>
> Key: MNG-6633
> URL: https://issues.apache.org/jira/browse/MNG-6633
> Project: Maven
> Issue Type: Bug
> Components: core
> Affects Versions: 3.6.0
> Reporter: Stefan Oehme
> Assignee: Sylwester Lachiewicz
> Priority: Major
> Fix For: 3.6.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> It takes the group and artifact ID of an Exclusion, concatenates them into a
> new String, which is kept in memory for the whole duration of the build and
> then compares that String against the concatenation of group and artifact ID
> of each incoming artifact, adding more CPU cycles than necessary. Instead it
> should just take the group and artifact ID from the Exclusion object and
> compare them against the group and artifact ID of the Artifact.
>
> For the 2000 module build I'm currently profiling, this is wasting over 1GB
> of RAM, with hundreds of thousands of duplicated Strings.
>
> See [https://github.com/apache/maven/pull/243]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
