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

Posted to issues@maven.apache.org by "cstamas (via GitHub)" <gi...@apache.org> on 2023/02/02 14:36:30 UTC

[GitHub] [maven-resolver] cstamas commented on pull request #166: [MRESOLVER-250] Wrap DataPool descriptors into weak refs

cstamas commented on PR #166:
URL: https://github.com/apache/maven-resolver/pull/166#issuecomment-1413843684

   This explanation sounds quite plausible, basically the lack of weak ref (added in this PR) preserved DefaultArtifact instances, that resulted in less instance to be created, less GC pressure.... OTOH, by looking at original JIRA, am unsure that "I observed a high heap consumption" is a real show stopper (I mean, if you do resolve huge dep trees, maybe you can expect somewhat bigger memory usage as well?). Ideally we could get some feedback from reporter...


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org