[
https://issues.apache.org/jira/browse/MNG-6571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749969#comment-16749969
]
Mickael Istria commented on MNG-6571:
-------------------------------------
Great job Herve!
I agree with [~YannLeCorse] that the BigInteger thing isn't worth chasing at
the moment since you found an "upstream" optimization that makes the BigInteger
almost invisible in overall memory consumption.
However, although it's not retained, we need to keep in mind that instantiating
a BigInteger takes more time than storing a long or a int, so f we want to get
into deep perf improvement, we must also take into account not only the number
of instances retained, but the overall number of object instantiated.
But that's another topic where a profiler will help prioritization more than a
heap dump.
> Maven memory consumption issue
> ------------------------------
>
> Key: MNG-6571
> URL: https://issues.apache.org/jira/browse/MNG-6571
> Project: Maven
> Issue Type: Wish
> Affects Versions: 3.6.0
> Reporter: Hervé Boutemy
> Priority: Major
> Attachments: Maven-Reactor-Dump-Patched.png, Maven-Reactor-Dump.png
>
>
> as reported on Users list:
> https://lists.apache.org/thread.html/7d75142448b3c234742bdfd3c743e2f62065fe8e0a313905cbbb2523@%3Cusers.maven.apache.org%3E
> then with details on Dev list:
> https://lists.apache.org/thread.html/34b64295238594e554f1f2f119848bce3b60d4e1e22e09f26aa64166@%3Cdev.maven.apache.org%3E
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
