I wonder if this fix also solves "remote shared parent" memory inefficiency described in https://issues.apache.org/jira/browse/MNG-5669
-- Regards, Igor On Tue, May 31, 2016, at 06:14 PM, Karl Heinz Marbaise wrote: > Hi, > > tested without the patch (-Xmx6g) ...run time for the test project more > than two 2 Minutes.... > > running with the patch (-Xmx1g): > > Run time ca. 27 seconds... > > also worked with -Xmx768m ...ca. 30 seconds... > > so looks very good... > > Let us wait what the IT's say... > > Kind regards > Karl Heinz Marbaise > > On 5/31/16 10:49 PM, Karl Heinz Marbaise wrote: > > Hi, > > > > after more investigation and an extremly good tip of Andriy...(see > > MNG-6030) and in the end the solution: > > > > Using test project with 5000 modules just doing: > > > > mvn clean > > > > using the patch now in master (41144e7ecf52e7ec3850f3e78d81f42f505f4af8) > > extremely reduces the memory footprint... > > > > https://github.com/khmarbaise/maven-test-project-generator/blob/master/Maven340-with-patch-5000.png > > > > > > This shows the result using the patch > > > > The following shows Maven 3.3.9: > > > > https://github.com/khmarbaise/maven-test-project-generator/blob/master/Maven339-5000.png > > > > > > Many thanks to Andriy for the support and help... > > > > we will see if not IT's will fail on the change. > > > > > > Kind regards > > Karl Heinz Marbaise > > > > On 4/22/16 9:49 PM, Karl Heinz Marbaise wrote: > >> Hi, > >> > >> i started a little bit more detailed analysis.. > >> > >> very simple via JConsole and running the different versions... > >> > >> I have summarized this here: > >> > >> https://github.com/khmarbaise/maven-test-project-generator > >> > >> Kind regards > >> Karl Heinz Marbaise > >> > >> On 4/17/16 5:50 PM, Karl Heinz Marbaise wrote: > >>> Hi to all, > >>> > >>> i have a question concerning the memory consumption... > >>> > >>> If i run maven with the same JDK and the same reactor and build with the > >>> same parameter and plugins... > >>> > >>> will the printout at the end of the build (Final Memory) something > >>> realiable about the consumption of the JVM during the build ?...Or is it > >>> at least a hint...or would i need to do something different (BTW: > >>> Someone has a hint about that?) ... > >>> > >>> > >>> [INFO] BUILD SUCCESS > >>> [INFO] > >>> ------------------------------------------------------------------------ > >>> [INFO] Total time: 6.431 s > >>> [INFO] Finished at: 2016-04-17T17:46:58+02:00 > >>> [INFO] Final Memory: 47M/638M > >>> > >>> So if i ran the same build with different Maven versions so could this > >>> give us a hint where more memory is consumed ...(to identify where and > >>> why is a different story)... > >>> > >>> Kind regards > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
