as discusses in the Jira issue, the cache on Version Range is simple and very
efficient
can someone review and second for merge to master?
Regards,
Hervé
Le mercredi 23 janvier 2019, 11:07:43 CET Hervé BOUTEMY a écrit :
> Hi,
>
> Interesting.
> I created MNG-6571 to track this issue: please m
I'm still computing the retained references but the first results look great.
Dump file once reactor is computed moved from 14Gb to 7.4Gb (I didn't let the
build run to the end).
Instances of VersionRange moved from 5 million to 6525. The cache has a
positive impact on the String instances, BigI
Hi,
Interesting.
I created MNG-6571 to track this issue: please move the memory dump on this
issue.
Then I created MNG-6571 branch [2] with a cache on VersionRange: this class is
currently immutable, then caching it is trivial. I don't know if it's the best
location, or if there are not other l
Hi,
I'm working on a huge project with plenty modules and we are facing a memory
consumption issue. We observed it when Maven computes the reactor and then
during the build itself.
Quick summary of our situation (as we can't share the POMs)
* We have a dedicated POM to manage all versi
