[
https://issues.apache.org/jira/browse/MNG-6632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Oehme updated MNG-6632:
------------------------------
Description:
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]
was:
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]
> 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
> Priority: Major
>
> 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)
