[ 
https://issues.apache.org/jira/browse/MNG-6632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069836#comment-17069836
 ] 

Hudson commented on MNG-6632:
-----------------------------

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/

> ArtifactHandlerManager.getArtifactHandler is inefficient
> --------------------------------------------------------
>
>                 Key: MNG-6632
>                 URL: https://issues.apache.org/jira/browse/MNG-6632
>             Project: Maven
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.6.0
>            Reporter: Stefan Oehme
>            Assignee: Herve Boutemy
>            Priority: Major
>             Fix For: 3.6.2
>
>
> I'm currently optimizing a very large (2000+ submodule) project. 
> ArtifactHandlerManager.getArtifactHandler is one of the CPU/memory hotspots, 
> because for every `get` call it goes through the Map injected by Plexus. This 
> Map has O( n ) lookup performance, because it is backed by an `Iterable`. It 
> would be much faster to remember the artifact handlers that have already been 
> found.
> See [https://github.com/apache/maven/pull/242]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to