[
https://issues.apache.org/jira/browse/MRESOLVER-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688547#comment-17688547
]
ASF GitHub Bot commented on MRESOLVER-320:
------------------------------------------
cstamas commented on PR #241:
URL: https://github.com/apache/maven-resolver/pull/241#issuecomment-1429907311
Reworked a bit: I simply hated the fact that this PR would potentially make
Resolver unable to calculate (some probably bigger graph) of dependencies in
case of confined memory, even at cost of 10% speed reduction.
Hence, reworked the PR a bit: added a config, that by default makes resolver
behave as with original patch (aggressive heap use, loose the 10% slow down),
but, in case the behavior can be returned the 1.8.x resolver way (using weak
pools).
> Investigate slower resolving speeds as reported by users
> --------------------------------------------------------
>
> Key: MRESOLVER-320
> URL: https://issues.apache.org/jira/browse/MRESOLVER-320
> Project: Maven Resolver
> Issue Type: Task
> Affects Versions: 1.9.4
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 1.9.5
>
>
> Users on ML reported "slowness" that MAY be caused by a change added in 1.9.0
> version of resolver MRESOLVER-250.
> [https://lists.apache.org/thread/r9p236z8kvqqk7ykvkgmc5wgps6n1hkf]
> [https://github.com/apache/maven-resolver/pull/166#issuecomment-1413808333]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
