You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2019/05/08 19:37:00 UTC

[jira] [Commented] (MNG-6632) ArtifactHandlerManager.getArtifactHandler is inefficient

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

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

Build succeeded in Jenkins: Maven TLP » maven » MNG-6069v2 #2

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6069v2/2/

> 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: Hervé 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
(v7.6.3#76005)