You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Karl Heinz Marbaise <kh...@gmx.de> on 2016/05/31 20:49:23 UTC
Re: Maven Memory Consumption
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-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Memory Consumption
Posted by Manfred Moser <ma...@simpligility.com>.
That sounds good to. Its awesome that this has been done and merged and will go out with the next release.
Manfred
Jason Dillon wrote on 2016-06-02 21:05:
> If its on by default I would expect folks to set
> MAVEN_OPTS=-Dmaven.logging=plain instead of magically making \u2014batch do that.
>
> If we mutate the cli api slightly to expose more details about the cli
> configuration to the Slf4jConfiguration then regular -Dmaven.logging=plain on
> command line would probably work too. �Right now the logging configuration has
> no context of the command-line params and can only use System.properties to
> fiddle with configuration.
>
> If ^^^ was done then could also consider adding \u2014color={yes|no} flag, though
> I felt odd hacking that in given that this is a pluggable aspect, and if you
> were using logbook backend it would be meaningless and potentially confusing.
>
> \u2014jason
>
>
> On June 2, 2016 at 8:37:18 PM, Manfred Moser (manfred@simpligility.com) wrote:
>
> If we plan to switch it to on be default at a later stage we could
> automatically disable it in batch mode. And tell people to run in batch mode on
> a CI server.
>
> Just a thought..
>
> Manfred
>
> Jason van Zyl wrote on 2016-06-02 19:52:
>
>> If the output comes out decently in color in CI consoles then it\u2019s probably
>>
>> not an issue putting the color on by default. But I haven\u2019t checked and
>> suggested that the color be off by default to start with.
>>
>>> On Jun 2, 2016, at 5:15 PM, Herv� BOUTEMY <he...@free.fr> wrote:
>>>
>>> I merged the PR in the slf4j-gossip branch (and added a little improvement)
>>>
>>> core ITs are ok (notice: ran without activating colors)
>>> colors for Linux are not exactly the same as the screen dump: yellow from the
>>>
>>> screen dump is bold white on Linux. This is ok for me
>>>
>>> Now, what's annoying is that:
>>> - color is not enabled by default: I had to configure MAVEN_OPTS="-
>>> Dmaven.logging=color"
>>> - when redirecting content to file, color is not disabled automatically
>>>
>>> I don't know if this is a showstopper or not
>>> I will continue to use it to see if there are unexpected side effects
>>>
>>> Regards,
>>>
>>> Herv�
>>>
>>> Le jeudi 2 juin 2016 09:21:46 Tam�s Cserven�k a �crit :
>>>> Olivier, if you refer to the slf4j-gossip branch, that IMHO Jason's PR
>>>> supersedes it.
>>>> Will drop that branch.
>>>>
>>>> On Thu, Jun 2, 2016 at 8:38 AM Olivier Lamy <ol...@apache.org> wrote:
>>>>> well I think this color stuff has already been done differently but never
>>>>> accepted......
>>>>>
>>>>> On 2 June 2016 at 16:28, Herv� BOUTEMY <he...@free.fr> wrote:
>>>>>> another feature that would be great for this release:
>>>>>> https://github.com/apache/maven/pull/81
>>>>>>
>>>>>> I still didn't have time to work on it, but I like the screenshot
>>>>>> The only thing that I'd like to check is: is tty detection working? ie
>>>>>
>>>>> does
>>>>>
>>>>>> color automatically disappear if there is no tty?
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Herv�
>>>>>>
>>>>>> Le jeudi 2 juin 2016 08:23:57 Herv� BOUTEMY a �crit :
>>>>>>> +1
>>>>>>> this is something that was often seen: this is great that it is fixed!
>>>>>>>
>>>>>>> For example, the last time I published Maven core site, the build
>>>>>
>>>>> simply
>>>>>
>>>>>>> failed because of PermgenSpace: now it is working like a charm...
>>>>>>>
>>>>>>> This release will be a must!
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Herv�
>>>>>>>
>>>>>>> Le mercredi 1 juin 2016 20:12:33 Karl Heinz Marbaise a �crit :
>>>>>>>> Hi Manfred,
>>>>>>>>
>>>>>>>> On 6/1/16 12:24 AM, Manfred Moser wrote:
>>>>>>>>> I can feel your excitement coming through in the emails.. ;-)
>>>>>>>>
>>>>>>>> Of course I'm excited ;-)
>>>>>>>>
>>>>>>>> ...cause it's very important...I have had heard many customers
>>>>>>>> saying
>>>>>>>> they will not upgrade to newer versions of Maven exactly based on
>>>>>
>>>>> such
>>>>>
>>>>>>>> issue(s)...
>>>>>>>>
>>>>>>>> which is in general bad ...
>>>>>>>>
>>>>>>>>
>>>>>>>> This will break their argument ;-)...
>>>>>>>>
>>>>>>>>> Karl Heinz Marbaise wrote on 2016-05-31 15:14:
>>>>>>>>>> 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
>>>>>>
>>>>>>>>>>> /M
>>>>>>>>>>> aven340-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
>>>>>>
>>>>>>>>>>> /M
>>>>>>>>>>> aven339-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-unsubscribe@maven.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>> --
>>>>> Olivier Lamy
>>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Takari and Apache Maven
>> http://twitter.com/jvanzyl
>> http://twitter.com/takari_io
>> ---------------------------------------------------------
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Memory Consumption
Posted by Jason Dillon <ja...@planet57.com>.
If its on by default I would expect folks to set MAVEN_OPTS=-Dmaven.logging=plain instead of magically making —batch do that.
If we mutate the cli api slightly to expose more details about the cli configuration to the Slf4jConfiguration then regular -Dmaven.logging=plain on command line would probably work too. Right now the logging configuration has no context of the command-line params and can only use System.properties to fiddle with configuration.
If ^^^ was done then could also consider adding —color={yes|no} flag, though I felt odd hacking that in given that this is a pluggable aspect, and if you were using logbook backend it would be meaningless and potentially confusing.
—jason
On June 2, 2016 at 8:37:18 PM, Manfred Moser (manfred@simpligility.com) wrote:
If we plan to switch it to on be default at a later stage we could automatically disable it in batch mode. And tell people to run in batch mode on a CI server.
Just a thought..
Manfred
Jason van Zyl wrote on 2016-06-02 19:52:
> If the output comes out decently in color in CI consoles then it’s probably
> not an issue putting the color on by default. But I haven’t checked and
> suggested that the color be off by default to start with.
>
>> On Jun 2, 2016, at 5:15 PM, Hervé BOUTEMY <he...@free.fr> wrote:
>>
>> I merged the PR in the slf4j-gossip branch (and added a little improvement)
>>
>> core ITs are ok (notice: ran without activating colors)
>> colors for Linux are not exactly the same as the screen dump: yellow from the
>> screen dump is bold white on Linux. This is ok for me
>>
>> Now, what's annoying is that:
>> - color is not enabled by default: I had to configure MAVEN_OPTS="-
>> Dmaven.logging=color"
>> - when redirecting content to file, color is not disabled automatically
>>
>> I don't know if this is a showstopper or not
>> I will continue to use it to see if there are unexpected side effects
>>
>> Regards,
>>
>> Hervé
>>
>> Le jeudi 2 juin 2016 09:21:46 Tamás Cservenák a écrit :
>>> Olivier, if you refer to the slf4j-gossip branch, that IMHO Jason's PR
>>> supersedes it.
>>> Will drop that branch.
>>>
>>> On Thu, Jun 2, 2016 at 8:38 AM Olivier Lamy <ol...@apache.org> wrote:
>>>> well I think this color stuff has already been done differently but never
>>>> accepted......
>>>>
>>>> On 2 June 2016 at 16:28, Hervé BOUTEMY <he...@free.fr> wrote:
>>>>> another feature that would be great for this release:
>>>>> https://github.com/apache/maven/pull/81
>>>>>
>>>>> I still didn't have time to work on it, but I like the screenshot
>>>>> The only thing that I'd like to check is: is tty detection working? ie
>>>>
>>>> does
>>>>
>>>>> color automatically disappear if there is no tty?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Hervé
>>>>>
>>>>> Le jeudi 2 juin 2016 08:23:57 Hervé BOUTEMY a écrit :
>>>>>> +1
>>>>>> this is something that was often seen: this is great that it is fixed!
>>>>>>
>>>>>> For example, the last time I published Maven core site, the build
>>>>
>>>> simply
>>>>
>>>>>> failed because of PermgenSpace: now it is working like a charm...
>>>>>>
>>>>>> This release will be a must!
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Hervé
>>>>>>
>>>>>> Le mercredi 1 juin 2016 20:12:33 Karl Heinz Marbaise a écrit :
>>>>>>> Hi Manfred,
>>>>>>>
>>>>>>> On 6/1/16 12:24 AM, Manfred Moser wrote:
>>>>>>>> I can feel your excitement coming through in the emails.. ;-)
>>>>>>>
>>>>>>> Of course I'm excited ;-)
>>>>>>>
>>>>>>> ...cause it's very important...I have had heard many customers
>>>>>>> saying
>>>>>>> they will not upgrade to newer versions of Maven exactly based on
>>>>
>>>> such
>>>>
>>>>>>> issue(s)...
>>>>>>>
>>>>>>> which is in general bad ...
>>>>>>>
>>>>>>>
>>>>>>> This will break their argument ;-)...
>>>>>>>
>>>>>>>> Karl Heinz Marbaise wrote on 2016-05-31 15:14:
>>>>>>>>> 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
>>>>>
>>>>>>>>>> /M
>>>>>>>>>> aven340-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
>>>>>
>>>>>>>>>> /M
>>>>>>>>>> aven339-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-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>> --
>>>> Olivier Lamy
>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Takari and Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Memory Consumption
Posted by Igor Fedorenko <ig...@ifedorenko.com>.
Somewhat related, Jason convinced me to opensource better logging
support for multithreaded builds I implemented some time ago.
https://github.com/takari/concurrent-build-logger
--
Regards,
Igor
On Thu, Jun 2, 2016, at 11:37 PM, Manfred Moser wrote:
> If we plan to switch it to on be default at a later stage we could
> automatically disable it in batch mode. And tell people to run in batch
> mode on a CI server.
>
> Just a thought..
>
> Manfred
>
> Jason van Zyl wrote on 2016-06-02 19:52:
>
> > If the output comes out decently in color in CI consoles then it’s probably
> > not an issue putting the color on by default. But I haven’t checked and
> > suggested that the color be off by default to start with.
> >
> >> On Jun 2, 2016, at 5:15 PM, Hervé BOUTEMY <he...@free.fr> wrote:
> >>
> >> I merged the PR in the slf4j-gossip branch (and added a little improvement)
> >>
> >> core ITs are ok (notice: ran without activating colors)
> >> colors for Linux are not exactly the same as the screen dump: yellow from the
> >> screen dump is bold white on Linux. This is ok for me
> >>
> >> Now, what's annoying is that:
> >> - color is not enabled by default: I had to configure MAVEN_OPTS="-
> >> Dmaven.logging=color"
> >> - when redirecting content to file, color is not disabled automatically
> >>
> >> I don't know if this is a showstopper or not
> >> I will continue to use it to see if there are unexpected side effects
> >>
> >> Regards,
> >>
> >> Hervé
> >>
> >> Le jeudi 2 juin 2016 09:21:46 Tamás Cservenák a écrit :
> >>> Olivier, if you refer to the slf4j-gossip branch, that IMHO Jason's PR
> >>> supersedes it.
> >>> Will drop that branch.
> >>>
> >>> On Thu, Jun 2, 2016 at 8:38 AM Olivier Lamy <ol...@apache.org> wrote:
> >>>> well I think this color stuff has already been done differently but never
> >>>> accepted......
> >>>>
> >>>> On 2 June 2016 at 16:28, Hervé BOUTEMY <he...@free.fr> wrote:
> >>>>> another feature that would be great for this release:
> >>>>> https://github.com/apache/maven/pull/81
> >>>>>
> >>>>> I still didn't have time to work on it, but I like the screenshot
> >>>>> The only thing that I'd like to check is: is tty detection working? ie
> >>>>
> >>>> does
> >>>>
> >>>>> color automatically disappear if there is no tty?
> >>>>>
> >>>>> Regards,
> >>>>>
> >>>>> Hervé
> >>>>>
> >>>>> Le jeudi 2 juin 2016 08:23:57 Hervé BOUTEMY a écrit :
> >>>>>> +1
> >>>>>> this is something that was often seen: this is great that it is fixed!
> >>>>>>
> >>>>>> For example, the last time I published Maven core site, the build
> >>>>
> >>>> simply
> >>>>
> >>>>>> failed because of PermgenSpace: now it is working like a charm...
> >>>>>>
> >>>>>> This release will be a must!
> >>>>>>
> >>>>>> Regards,
> >>>>>>
> >>>>>> Hervé
> >>>>>>
> >>>>>> Le mercredi 1 juin 2016 20:12:33 Karl Heinz Marbaise a écrit :
> >>>>>>> Hi Manfred,
> >>>>>>>
> >>>>>>> On 6/1/16 12:24 AM, Manfred Moser wrote:
> >>>>>>>> I can feel your excitement coming through in the emails.. ;-)
> >>>>>>>
> >>>>>>> Of course I'm excited ;-)
> >>>>>>>
> >>>>>>> ...cause it's very important...I have had heard many customers
> >>>>>>> saying
> >>>>>>> they will not upgrade to newer versions of Maven exactly based on
> >>>>
> >>>> such
> >>>>
> >>>>>>> issue(s)...
> >>>>>>>
> >>>>>>> which is in general bad ...
> >>>>>>>
> >>>>>>>
> >>>>>>> This will break their argument ;-)...
> >>>>>>>
> >>>>>>>> Karl Heinz Marbaise wrote on 2016-05-31 15:14:
> >>>>>>>>> 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
> >>>>>
> >>>>>>>>>> /M
> >>>>>>>>>> aven340-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
> >>>>>
> >>>>>>>>>> /M
> >>>>>>>>>> aven339-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-unsubscribe@maven.apache.org
> >>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>
> >>>> --
> >>>> Olivier Lamy
> >>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >
> > Thanks,
> >
> > Jason
> >
> > ----------------------------------------------------------
> > Jason van Zyl
> > Founder, Takari and Apache Maven
> > http://twitter.com/jvanzyl
> > http://twitter.com/takari_io
> > ---------------------------------------------------------
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Memory Consumption
Posted by Manfred Moser <ma...@simpligility.com>.
If we plan to switch it to on be default at a later stage we could automatically disable it in batch mode. And tell people to run in batch mode on a CI server.
Just a thought..
Manfred
Jason van Zyl wrote on 2016-06-02 19:52:
> If the output comes out decently in color in CI consoles then it\u2019s probably
> not an issue putting the color on by default. But I haven\u2019t checked and
> suggested that the color be off by default to start with.
>
>> On Jun 2, 2016, at 5:15 PM, Herv� BOUTEMY <he...@free.fr> wrote:
>>
>> I merged the PR in the slf4j-gossip branch (and added a little improvement)
>>
>> core ITs are ok (notice: ran without activating colors)
>> colors for Linux are not exactly the same as the screen dump: yellow from the
>> screen dump is bold white on Linux. This is ok for me
>>
>> Now, what's annoying is that:
>> - color is not enabled by default: I had to configure MAVEN_OPTS="-
>> Dmaven.logging=color"
>> - when redirecting content to file, color is not disabled automatically
>>
>> I don't know if this is a showstopper or not
>> I will continue to use it to see if there are unexpected side effects
>>
>> Regards,
>>
>> Herv�
>>
>> Le jeudi 2 juin 2016 09:21:46 Tam�s Cserven�k a �crit :
>>> Olivier, if you refer to the slf4j-gossip branch, that IMHO Jason's PR
>>> supersedes it.
>>> Will drop that branch.
>>>
>>> On Thu, Jun 2, 2016 at 8:38 AM Olivier Lamy <ol...@apache.org> wrote:
>>>> well I think this color stuff has already been done differently but never
>>>> accepted......
>>>>
>>>> On 2 June 2016 at 16:28, Herv� BOUTEMY <he...@free.fr> wrote:
>>>>> another feature that would be great for this release:
>>>>> https://github.com/apache/maven/pull/81
>>>>>
>>>>> I still didn't have time to work on it, but I like the screenshot
>>>>> The only thing that I'd like to check is: is tty detection working? ie
>>>>
>>>> does
>>>>
>>>>> color automatically disappear if there is no tty?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Herv�
>>>>>
>>>>> Le jeudi 2 juin 2016 08:23:57 Herv� BOUTEMY a �crit :
>>>>>> +1
>>>>>> this is something that was often seen: this is great that it is fixed!
>>>>>>
>>>>>> For example, the last time I published Maven core site, the build
>>>>
>>>> simply
>>>>
>>>>>> failed because of PermgenSpace: now it is working like a charm...
>>>>>>
>>>>>> This release will be a must!
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Herv�
>>>>>>
>>>>>> Le mercredi 1 juin 2016 20:12:33 Karl Heinz Marbaise a �crit :
>>>>>>> Hi Manfred,
>>>>>>>
>>>>>>> On 6/1/16 12:24 AM, Manfred Moser wrote:
>>>>>>>> I can feel your excitement coming through in the emails.. ;-)
>>>>>>>
>>>>>>> Of course I'm excited ;-)
>>>>>>>
>>>>>>> ...cause it's very important...I have had heard many customers
>>>>>>> saying
>>>>>>> they will not upgrade to newer versions of Maven exactly based on
>>>>
>>>> such
>>>>
>>>>>>> issue(s)...
>>>>>>>
>>>>>>> which is in general bad ...
>>>>>>>
>>>>>>>
>>>>>>> This will break their argument ;-)...
>>>>>>>
>>>>>>>> Karl Heinz Marbaise wrote on 2016-05-31 15:14:
>>>>>>>>> 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
>>>>>
>>>>>>>>>> /M
>>>>>>>>>> aven340-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
>>>>>
>>>>>>>>>> /M
>>>>>>>>>> aven339-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-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>> --
>>>> Olivier Lamy
>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Takari and Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Memory Consumption
Posted by Jason van Zyl <ja...@takari.io>.
If the output comes out decently in color in CI consoles then it’s probably not an issue putting the color on by default. But I haven’t checked and suggested that the color be off by default to start with.
> On Jun 2, 2016, at 5:15 PM, Hervé BOUTEMY <he...@free.fr> wrote:
>
> I merged the PR in the slf4j-gossip branch (and added a little improvement)
>
> core ITs are ok (notice: ran without activating colors)
> colors for Linux are not exactly the same as the screen dump: yellow from the
> screen dump is bold white on Linux. This is ok for me
>
> Now, what's annoying is that:
> - color is not enabled by default: I had to configure MAVEN_OPTS="-
> Dmaven.logging=color"
> - when redirecting content to file, color is not disabled automatically
>
> I don't know if this is a showstopper or not
> I will continue to use it to see if there are unexpected side effects
>
> Regards,
>
> Hervé
>
> Le jeudi 2 juin 2016 09:21:46 Tamás Cservenák a écrit :
>> Olivier, if you refer to the slf4j-gossip branch, that IMHO Jason's PR
>> supersedes it.
>> Will drop that branch.
>>
>> On Thu, Jun 2, 2016 at 8:38 AM Olivier Lamy <ol...@apache.org> wrote:
>>> well I think this color stuff has already been done differently but never
>>> accepted......
>>>
>>> On 2 June 2016 at 16:28, Hervé BOUTEMY <he...@free.fr> wrote:
>>>> another feature that would be great for this release:
>>>> https://github.com/apache/maven/pull/81
>>>>
>>>> I still didn't have time to work on it, but I like the screenshot
>>>> The only thing that I'd like to check is: is tty detection working? ie
>>>
>>> does
>>>
>>>> color automatically disappear if there is no tty?
>>>>
>>>> Regards,
>>>>
>>>> Hervé
>>>>
>>>> Le jeudi 2 juin 2016 08:23:57 Hervé BOUTEMY a écrit :
>>>>> +1
>>>>> this is something that was often seen: this is great that it is fixed!
>>>>>
>>>>> For example, the last time I published Maven core site, the build
>>>
>>> simply
>>>
>>>>> failed because of PermgenSpace: now it is working like a charm...
>>>>>
>>>>> This release will be a must!
>>>>>
>>>>> Regards,
>>>>>
>>>>> Hervé
>>>>>
>>>>> Le mercredi 1 juin 2016 20:12:33 Karl Heinz Marbaise a écrit :
>>>>>> Hi Manfred,
>>>>>>
>>>>>> On 6/1/16 12:24 AM, Manfred Moser wrote:
>>>>>>> I can feel your excitement coming through in the emails.. ;-)
>>>>>>
>>>>>> Of course I'm excited ;-)
>>>>>>
>>>>>> ...cause it's very important...I have had heard many customers
>>>>>> saying
>>>>>> they will not upgrade to newer versions of Maven exactly based on
>>>
>>> such
>>>
>>>>>> issue(s)...
>>>>>>
>>>>>> which is in general bad ...
>>>>>>
>>>>>>
>>>>>> This will break their argument ;-)...
>>>>>>
>>>>>>> Karl Heinz Marbaise wrote on 2016-05-31 15:14:
>>>>>>>> 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
>>>>
>>>>>>>>> /M
>>>>>>>>> aven340-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
>>>>
>>>>>>>>> /M
>>>>>>>>> aven339-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-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>> --
>>> Olivier Lamy
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Memory Consumption
Posted by Jason Dillon <ja...@planet57.com>.
colors for Linux are not exactly the same as the screen dump: yellow from the
screen dump is bold white on Linux. This is ok for me
Terminals can render whatever colors they want for the ANSI colors and many have this configurable.
To be clear my terminal env has bold color rendering as yellow (very very very old preference I’ve had for a long time so much I forgot it was my preference).
We can certainly make things explicitly yellow though if that is preferred over simply bold.
—jason
Re: Maven Memory Consumption
Posted by Jason Dillon <ja...@planet57.com>.
On June 2, 2016 at 3:15:35 PM, Hervé BOUTEMY (herve.boutemy@free.fr) wrote:
I merged the PR in the slf4j-gossip branch (and added a little improvement)
core ITs are ok (notice: ran without activating colors)
The testsuite certainly will not be very happy with color enabled as many tests are expecting exact strings in the output. I had considered setting MAVEN_SKIP_RC env-var to avoid any local customization from polluting the testsuite execution.
colors for Linux are not exactly the same as the screen dump: yellow from the
screen dump is bold white on Linux. This is ok for me
Terminals can render whatever colors they want for the ANSI colors and many have this configurable.
Now, what's annoying is that:
- color is not enabled by default: I had to configure MAVEN_OPTS="-
Dmaven.logging=color"
Seemed safer off by default then breaking the output for users where ansi is not supported and for whatever reason its not been detected as such to strip out.
- when redirecting content to file, color is not disabled automatically
It may depend on how its redirected, my local testing shows that `mvn > foo’ disables ansi sequences, though I can not say I’ve done any exhaustive testing of this.
To be able to tell if System.out is an ANSI-aware terminal it may need a bit more love ala jline or more helpers in jansi to do more properly?
—jason
Re: Maven Memory Consumption
Posted by Hervé BOUTEMY <he...@free.fr>.
I merged the PR in the slf4j-gossip branch (and added a little improvement)
core ITs are ok (notice: ran without activating colors)
colors for Linux are not exactly the same as the screen dump: yellow from the
screen dump is bold white on Linux. This is ok for me
Now, what's annoying is that:
- color is not enabled by default: I had to configure MAVEN_OPTS="-
Dmaven.logging=color"
- when redirecting content to file, color is not disabled automatically
I don't know if this is a showstopper or not
I will continue to use it to see if there are unexpected side effects
Regards,
Hervé
Le jeudi 2 juin 2016 09:21:46 Tamás Cservenák a écrit :
> Olivier, if you refer to the slf4j-gossip branch, that IMHO Jason's PR
> supersedes it.
> Will drop that branch.
>
> On Thu, Jun 2, 2016 at 8:38 AM Olivier Lamy <ol...@apache.org> wrote:
> > well I think this color stuff has already been done differently but never
> > accepted......
> >
> > On 2 June 2016 at 16:28, Hervé BOUTEMY <he...@free.fr> wrote:
> > > another feature that would be great for this release:
> > > https://github.com/apache/maven/pull/81
> > >
> > > I still didn't have time to work on it, but I like the screenshot
> > > The only thing that I'd like to check is: is tty detection working? ie
> >
> > does
> >
> > > color automatically disappear if there is no tty?
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le jeudi 2 juin 2016 08:23:57 Hervé BOUTEMY a écrit :
> > > > +1
> > > > this is something that was often seen: this is great that it is fixed!
> > > >
> > > > For example, the last time I published Maven core site, the build
> >
> > simply
> >
> > > > failed because of PermgenSpace: now it is working like a charm...
> > > >
> > > > This release will be a must!
> > > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > > Le mercredi 1 juin 2016 20:12:33 Karl Heinz Marbaise a écrit :
> > > > > Hi Manfred,
> > > > >
> > > > > On 6/1/16 12:24 AM, Manfred Moser wrote:
> > > > > > I can feel your excitement coming through in the emails.. ;-)
> > > > >
> > > > > Of course I'm excited ;-)
> > > > >
> > > > > ...cause it's very important...I have had heard many customers
> > > > > saying
> > > > > they will not upgrade to newer versions of Maven exactly based on
> >
> > such
> >
> > > > > issue(s)...
> > > > >
> > > > > which is in general bad ...
> > > > >
> > > > >
> > > > > This will break their argument ;-)...
> > > > >
> > > > > > Karl Heinz Marbaise wrote on 2016-05-31 15:14:
> > > > > >> 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
> > >
> > > > > >>> /M
> > > > > >>> aven340-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
> > >
> > > > > >>> /M
> > > > > >>> aven339-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-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> >
> > --
> > Olivier Lamy
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Memory Consumption
Posted by Tamás Cservenák <ta...@cservenak.net>.
Olivier, if you refer to the slf4j-gossip branch, that IMHO Jason's PR
supersedes it.
Will drop that branch.
On Thu, Jun 2, 2016 at 8:38 AM Olivier Lamy <ol...@apache.org> wrote:
> well I think this color stuff has already been done differently but never
> accepted......
>
> On 2 June 2016 at 16:28, Hervé BOUTEMY <he...@free.fr> wrote:
>
> > another feature that would be great for this release:
> > https://github.com/apache/maven/pull/81
> >
> > I still didn't have time to work on it, but I like the screenshot
> > The only thing that I'd like to check is: is tty detection working? ie
> does
> > color automatically disappear if there is no tty?
> >
> > Regards,
> >
> > Hervé
> >
> > Le jeudi 2 juin 2016 08:23:57 Hervé BOUTEMY a écrit :
> > > +1
> > > this is something that was often seen: this is great that it is fixed!
> > >
> > > For example, the last time I published Maven core site, the build
> simply
> > > failed because of PermgenSpace: now it is working like a charm...
> > >
> > > This release will be a must!
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le mercredi 1 juin 2016 20:12:33 Karl Heinz Marbaise a écrit :
> > > > Hi Manfred,
> > > >
> > > > On 6/1/16 12:24 AM, Manfred Moser wrote:
> > > > > I can feel your excitement coming through in the emails.. ;-)
> > > >
> > > > Of course I'm excited ;-)
> > > >
> > > > ...cause it's very important...I have had heard many customers saying
> > > > they will not upgrade to newer versions of Maven exactly based on
> such
> > > > issue(s)...
> > > >
> > > > which is in general bad ...
> > > >
> > > >
> > > > This will break their argument ;-)...
> > > >
> > > > > Karl Heinz Marbaise wrote on 2016-05-31 15:14:
> > > > >> 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
> > > > >>> /M
> > > > >>> aven340-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
> > > > >>> /M
> > > > >>> aven339-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-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
Re: Maven Memory Consumption
Posted by Olivier Lamy <ol...@apache.org>.
well I think this color stuff has already been done differently but never
accepted......
On 2 June 2016 at 16:28, Hervé BOUTEMY <he...@free.fr> wrote:
> another feature that would be great for this release:
> https://github.com/apache/maven/pull/81
>
> I still didn't have time to work on it, but I like the screenshot
> The only thing that I'd like to check is: is tty detection working? ie does
> color automatically disappear if there is no tty?
>
> Regards,
>
> Hervé
>
> Le jeudi 2 juin 2016 08:23:57 Hervé BOUTEMY a écrit :
> > +1
> > this is something that was often seen: this is great that it is fixed!
> >
> > For example, the last time I published Maven core site, the build simply
> > failed because of PermgenSpace: now it is working like a charm...
> >
> > This release will be a must!
> >
> > Regards,
> >
> > Hervé
> >
> > Le mercredi 1 juin 2016 20:12:33 Karl Heinz Marbaise a écrit :
> > > Hi Manfred,
> > >
> > > On 6/1/16 12:24 AM, Manfred Moser wrote:
> > > > I can feel your excitement coming through in the emails.. ;-)
> > >
> > > Of course I'm excited ;-)
> > >
> > > ...cause it's very important...I have had heard many customers saying
> > > they will not upgrade to newer versions of Maven exactly based on such
> > > issue(s)...
> > >
> > > which is in general bad ...
> > >
> > >
> > > This will break their argument ;-)...
> > >
> > > > Karl Heinz Marbaise wrote on 2016-05-31 15:14:
> > > >> 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
> > > >>> /M
> > > >>> aven340-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
> > > >>> /M
> > > >>> aven339-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-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Maven Memory Consumption
Posted by Hervé BOUTEMY <he...@free.fr>.
another feature that would be great for this release:
https://github.com/apache/maven/pull/81
I still didn't have time to work on it, but I like the screenshot
The only thing that I'd like to check is: is tty detection working? ie does
color automatically disappear if there is no tty?
Regards,
Hervé
Le jeudi 2 juin 2016 08:23:57 Hervé BOUTEMY a écrit :
> +1
> this is something that was often seen: this is great that it is fixed!
>
> For example, the last time I published Maven core site, the build simply
> failed because of PermgenSpace: now it is working like a charm...
>
> This release will be a must!
>
> Regards,
>
> Hervé
>
> Le mercredi 1 juin 2016 20:12:33 Karl Heinz Marbaise a écrit :
> > Hi Manfred,
> >
> > On 6/1/16 12:24 AM, Manfred Moser wrote:
> > > I can feel your excitement coming through in the emails.. ;-)
> >
> > Of course I'm excited ;-)
> >
> > ...cause it's very important...I have had heard many customers saying
> > they will not upgrade to newer versions of Maven exactly based on such
> > issue(s)...
> >
> > which is in general bad ...
> >
> >
> > This will break their argument ;-)...
> >
> > > Karl Heinz Marbaise wrote on 2016-05-31 15:14:
> > >> 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
> > >>> /M
> > >>> aven340-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
> > >>> /M
> > >>> aven339-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-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Memory Consumption
Posted by Hervé BOUTEMY <he...@free.fr>.
+1
this is something that was often seen: this is great that it is fixed!
For example, the last time I published Maven core site, the build simply
failed because of PermgenSpace: now it is working like a charm...
This release will be a must!
Regards,
Hervé
Le mercredi 1 juin 2016 20:12:33 Karl Heinz Marbaise a écrit :
> Hi Manfred,
>
> On 6/1/16 12:24 AM, Manfred Moser wrote:
> > I can feel your excitement coming through in the emails.. ;-)
>
> Of course I'm excited ;-)
>
> ...cause it's very important...I have had heard many customers saying
> they will not upgrade to newer versions of Maven exactly based on such
> issue(s)...
>
> which is in general bad ...
>
>
> This will break their argument ;-)...
>
> > Karl Heinz Marbaise wrote on 2016-05-31 15:14:
> >> 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/M
> >>> aven340-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/M
> >>> aven339-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-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Memory Consumption
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Manfred,
On 6/1/16 12:24 AM, Manfred Moser wrote:
> I can feel your excitement coming through in the emails.. ;-)
Of course I'm excited ;-)
...cause it's very important...I have had heard many customers saying
they will not upgrade to newer versions of Maven exactly based on such
issue(s)...
which is in general bad ...
This will break their argument ;-)...
>
> Karl Heinz Marbaise wrote on 2016-05-31 15:14:
>
>> 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-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Memory Consumption
Posted by Manfred Moser <ma...@simpligility.com>.
I can feel your excitement coming through in the emails.. ;-)
Karl Heinz Marbaise wrote on 2016-05-31 15:14:
> 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-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Memory Consumption
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Igor,
On 6/3/16 5:27 AM, Igor Fedorenko wrote:
> I wonder if this fix also solves "remote shared parent" memory
> inefficiency described in https://issues.apache.org/jira/browse/MNG-5669
So doing some research...
The DefaultProjectBuilder contains a method:
private ModelData readParent( Model childModel, ModelSource childSource,
ModelBuildingRequest request,
DefaultModelProblemCollector problems )
which is called for each module...
The information for the parent is cached ...So this looks to me it is
fixed...but it is done before and is not related to MNG-6030...
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Memory Consumption
Posted by Igor Fedorenko <ig...@ifedorenko.com>.
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-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Memory Consumption
Posted by Kristian Rosenvold <kr...@gmail.com>.
I somehow assume the original patch that caused this behaviour was created
due to memory leaks in embedded mode. Do de have any way to handle both ?
(I'm wondering if we have any scope that is bound to the current embedsed
execution....)
(I'm all i favour of this change no matter what...)
Kristian
1. jun. 2016 12.15 a.m. skrev "Karl Heinz Marbaise" <kh...@gmx.de>:
> 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-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Maven Memory Consumption
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
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-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org