maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <j...@apache.org>
Subject [jira] [Commented] (MNG-6571) Maven memory consumption issue
Date Wed, 23 Jan 2019 13:13:01 GMT

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

Hervé Boutemy commented on MNG-6571:
------------------------------------

[~mickael.istria] I hoped you'd be interested :)
FYI, I was yesterday at ParisJUG session https://www.parisjug.org/xwiki/wiki/oldversion/view/Meeting/20190121
and this pattern was one of the topics explained during the "Revisiting Effective Java in
2019" talk :)

for BigIntegers, VersionRange will drastically reduce the number of ComparableVersion instances
But you're right: we could probably optimize ComparableVersion code to check if the number
parser is small enough to be represented as an int or long: the biggest numbers we get usually
is the timestamp of a SNAPSHOT, like 20171015.230843, then an int would be sufficient

> 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)

Mime
View raw message