Re: Speed of Maven build

[Manfred Moser]

Mickael Istria wrote on 2020-08-25 14:17 (GMT -07:00):

> I
> 
> On Tuesday, August 25, 2020, Manfred Moser  wrote:
>> And the VS code integration from Red Hat might also do something along
> those lines.
> 
> It embeds and uses m2eclipse.
> 

Haha.. thanks for confirming. I thought that to be the case but did not want to 
say it explicitly since I was only 80 or so percent sure.. 

manfred

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Speed of Maven build

[Mickael Istria]

I

On Tuesday, August 25, 2020, Manfred Moser  wrote:
> And the VS code integration from Red Hat might also do something along
those lines.

It embeds and uses m2eclipse.

-- 
Mickael Istria
Eclipse IDE 
developer, for Red Hat Developers 

Re: Speed of Maven build

[Falko Modler]

Maybe slightly offtopic but if you have (many) submodules, you might
want to consider automatic incremental builds (based on SCM changes)
with https://github.com/vackosar/gitflow-incremental-builder

Don't be scared by the name. You do not actually need a gitflow branch
layout.

Disclaimer: I am maintaining gitflow-incremental-builder.

Cheers,

Falko

PS: IIRC, a few months ago someone on this mailing list came up with an
idea to "cache" build results with Maven. Not sure what happened to that
idea.

Am 25.08.2020 um 23:07 schrieb Manfred Moser:

Also the M2Eclipse integration does basically embed maven and make the Maven 
build incremental.

The Takari plugin does that on the commandline with the eclipse compiler

And the VS code integration from Red Hat might also do something along those 
lines.

Others can chime in with more details.

Manfred

John Patrick wrote on 2020-08-25 13:29 (GMT -07:00):


Are you planning to create a baseline project or selecting a range of
projects to be used as a baseline, so that perceived improvements can
be monitored? So that anyone wanting to help out or give feedback can
submit their own build performance.

i.e.
1. Equipment OS, Ram, CPU, physical, virtual, docker, openshift, other
2. Java version
3. Maven version
4. Speedtest results
5. Direct Internet Connection or via Http Proxy or via Nexus/Artifactory
6. Clean/Fresh Local Repo Execution Time
7. 2nd Execution Time, after everything downloaded

As using Maven since 2005, I've found each new release has gotten
faster and faster, and most performance issues have been around what
OS I'm using, SSD vs HDD and also do you have enough free RAM etc.

As I'm surprised how quickly my builds are running at the moment, the
only issue is when I see maven perform internet connections
downloading new dependencies or say the versions plugin to check. Any
thoughts about adding a HTTP/2 Server Push support so if it's Maven
Aware and you request the pom it can also push back the hashes and
maybe the jar too.

Regarding a "zombie" maven instance, it should be opt in so i need to
explicitly enable it as often i'm jumping around between lots of
projects so don't want each having a "zombie" progress and i might not
be building that project again for another week maybe.

John

On Tue, 25 Aug 2020 at 12:27, Jeff Jensen
 wrote:

In case this helps, Jason Dillon has a "Maven Shell" that does what you
seek for CLI - launches a Maven instance and runs interactive commands with
it, saving the startup time.
https://github.com/jdillon/mvnsh


On Tue, Aug 25, 2020 at 12:27 AM Jaroslav Tulach 
wrote:


And it's Apache Maven, over the corner at https://maven.apache.org/ so
I suppose that community would be happy to get such contributions.

-Bertrand

You are right, Bertrand. Why not ask!

Hello Maven guys,
we had a discussion on the NetBeans mailing list recently and here is a
summary:
* Apache NetBeans IDE is delegating most of its work directly to Maven
* Users however complain that the speed isn't great
* One of the ideas was to launch a "zombie" instance of Maven in advance
* then actions like build, exec or test would be faster

Have you thought about something like this already? Any advices?

Best regards.
Jaroslav Tulach
NetBeans Platform Architect

ne 23. 8. 2020 v 9:06 odesílatel Jaroslav Tulach <
jaroslav.tul...@gmail.com>
napsal:


I agree with others, Ant is much faster day to day. But the pom.xml has
become the universal project file for Java,

Thank you all for sharing your thoughts. I know Maven start is slower,

but

I
learned to live with it. It is interesting to hear that some of you
maintain a
dual Ant based copy of your project metadata. Once we were trying a
different
approach:

There is a way to speed Maven in the IDE. Launch Maven, let it read all
XML &
co. files and stop it. As soon as we need to build/run/test, wake up this
zombie Maven process, tell it what to do and let it continue. If the XML
files
are modified, throw the process away and initialize it again. Tomáš

Stupka

implemented a prototype of this and there were no issues, as far as I

know

(nobody tested it thoroughly however).

Maybe the support is even in and there is a property to turn it on. If

the

Maven startup is the biggest problem for you guys, we shall investigate
how to
turn Tomáš's work on...

-jt







-
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




-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Speed of Maven build

[Manfred Moser]

Also the M2Eclipse integration does basically embed maven and make the Maven 
build incremental.

The Takari plugin does that on the commandline with the eclipse compiler

And the VS code integration from Red Hat might also do something along those 
lines.

Others can chime in with more details.

Manfred

John Patrick wrote on 2020-08-25 13:29 (GMT -07:00):

> Are you planning to create a baseline project or selecting a range of
> projects to be used as a baseline, so that perceived improvements can
> be monitored? So that anyone wanting to help out or give feedback can
> submit their own build performance.
> 
> i.e.
> 1. Equipment OS, Ram, CPU, physical, virtual, docker, openshift, other
> 2. Java version
> 3. Maven version
> 4. Speedtest results
> 5. Direct Internet Connection or via Http Proxy or via Nexus/Artifactory
> 6. Clean/Fresh Local Repo Execution Time
> 7. 2nd Execution Time, after everything downloaded
> 
> As using Maven since 2005, I've found each new release has gotten
> faster and faster, and most performance issues have been around what
> OS I'm using, SSD vs HDD and also do you have enough free RAM etc.
> 
> As I'm surprised how quickly my builds are running at the moment, the
> only issue is when I see maven perform internet connections
> downloading new dependencies or say the versions plugin to check. Any
> thoughts about adding a HTTP/2 Server Push support so if it's Maven
> Aware and you request the pom it can also push back the hashes and
> maybe the jar too.
> 
> Regarding a "zombie" maven instance, it should be opt in so i need to
> explicitly enable it as often i'm jumping around between lots of
> projects so don't want each having a "zombie" progress and i might not
> be building that project again for another week maybe.
> 
> John
> 
> On Tue, 25 Aug 2020 at 12:27, Jeff Jensen
>  wrote:
>>
>> In case this helps, Jason Dillon has a "Maven Shell" that does what you
>> seek for CLI - launches a Maven instance and runs interactive commands with
>> it, saving the startup time.
>> https://github.com/jdillon/mvnsh
>>
>>
>> On Tue, Aug 25, 2020 at 12:27 AM Jaroslav Tulach 
>> wrote:
>>
>> > > And it's Apache Maven, over the corner at https://maven.apache.org/ so
>> > > I suppose that community would be happy to get such contributions.
>> > >
>> > > -Bertrand
>> >
>> > You are right, Bertrand. Why not ask!
>> >
>> > Hello Maven guys,
>> > we had a discussion on the NetBeans mailing list recently and here is a
>> > summary:
>> > * Apache NetBeans IDE is delegating most of its work directly to Maven
>> > * Users however complain that the speed isn't great
>> > * One of the ideas was to launch a "zombie" instance of Maven in advance
>> > * then actions like build, exec or test would be faster
>> >
>> > Have you thought about something like this already? Any advices?
>> >
>> > Best regards.
>> > Jaroslav Tulach
>> > NetBeans Platform Architect
>> >
>> > ne 23. 8. 2020 v 9:06 odesílatel Jaroslav Tulach <
>> > jaroslav.tul...@gmail.com>
>> > napsal:
>> >
>> > > > I agree with others, Ant is much faster day to day. But the pom.xml has
>> > > > become the universal project file for Java,
>> > >
>> > > Thank you all for sharing your thoughts. I know Maven start is slower,
>> > but
>> > > I
>> > > learned to live with it. It is interesting to hear that some of you
>> > > maintain a
>> > > dual Ant based copy of your project metadata. Once we were trying a
>> > > different
>> > > approach:
>> > >
>> > > There is a way to speed Maven in the IDE. Launch Maven, let it read all
>> > > XML &
>> > > co. files and stop it. As soon as we need to build/run/test, wake up this
>> > > zombie Maven process, tell it what to do and let it continue. If the XML
>> > > files
>> > > are modified, throw the process away and initialize it again. Tomáš
>> > Stupka
>> > > implemented a prototype of this and there were no issues, as far as I
>> > know
>> > > (nobody tested it thoroughly however).
>> > >
>> > > Maybe the support is even in and there is a property to turn it on. If
>> > the
>> > > Maven startup is the biggest problem for you guys, we shall investigate
>> > > how to
>> > > turn Tomáš's work on...
>> > >
>> > > -jt
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> >
> 
> -
> 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

Re: Speed of Maven build

[John Patrick]

Are you planning to create a baseline project or selecting a range of
projects to be used as a baseline, so that perceived improvements can
be monitored? So that anyone wanting to help out or give feedback can
submit their own build performance.

i.e.
1. Equipment OS, Ram, CPU, physical, virtual, docker, openshift, other
2. Java version
3. Maven version
4. Speedtest results
5. Direct Internet Connection or via Http Proxy or via Nexus/Artifactory
6. Clean/Fresh Local Repo Execution Time
7. 2nd Execution Time, after everything downloaded

As using Maven since 2005, I've found each new release has gotten
faster and faster, and most performance issues have been around what
OS I'm using, SSD vs HDD and also do you have enough free RAM etc.

As I'm surprised how quickly my builds are running at the moment, the
only issue is when I see maven perform internet connections
downloading new dependencies or say the versions plugin to check. Any
thoughts about adding a HTTP/2 Server Push support so if it's Maven
Aware and you request the pom it can also push back the hashes and
maybe the jar too.

Regarding a "zombie" maven instance, it should be opt in so i need to
explicitly enable it as often i'm jumping around between lots of
projects so don't want each having a "zombie" progress and i might not
be building that project again for another week maybe.

John

On Tue, 25 Aug 2020 at 12:27, Jeff Jensen
 wrote:
>
> In case this helps, Jason Dillon has a "Maven Shell" that does what you
> seek for CLI - launches a Maven instance and runs interactive commands with
> it, saving the startup time.
> https://github.com/jdillon/mvnsh
>
>
> On Tue, Aug 25, 2020 at 12:27 AM Jaroslav Tulach 
> wrote:
>
> > > And it's Apache Maven, over the corner at https://maven.apache.org/ so
> > > I suppose that community would be happy to get such contributions.
> > >
> > > -Bertrand
> >
> > You are right, Bertrand. Why not ask!
> >
> > Hello Maven guys,
> > we had a discussion on the NetBeans mailing list recently and here is a
> > summary:
> > * Apache NetBeans IDE is delegating most of its work directly to Maven
> > * Users however complain that the speed isn't great
> > * One of the ideas was to launch a "zombie" instance of Maven in advance
> > * then actions like build, exec or test would be faster
> >
> > Have you thought about something like this already? Any advices?
> >
> > Best regards.
> > Jaroslav Tulach
> > NetBeans Platform Architect
> >
> > ne 23. 8. 2020 v 9:06 odesílatel Jaroslav Tulach <
> > jaroslav.tul...@gmail.com>
> > napsal:
> >
> > > > I agree with others, Ant is much faster day to day. But the pom.xml has
> > > > become the universal project file for Java,
> > >
> > > Thank you all for sharing your thoughts. I know Maven start is slower,
> > but
> > > I
> > > learned to live with it. It is interesting to hear that some of you
> > > maintain a
> > > dual Ant based copy of your project metadata. Once we were trying a
> > > different
> > > approach:
> > >
> > > There is a way to speed Maven in the IDE. Launch Maven, let it read all
> > > XML &
> > > co. files and stop it. As soon as we need to build/run/test, wake up this
> > > zombie Maven process, tell it what to do and let it continue. If the XML
> > > files
> > > are modified, throw the process away and initialize it again. Tomáš
> > Stupka
> > > implemented a prototype of this and there were no issues, as far as I
> > know
> > > (nobody tested it thoroughly however).
> > >
> > > Maybe the support is even in and there is a property to turn it on. If
> > the
> > > Maven startup is the biggest problem for you guys, we shall investigate
> > > how to
> > > turn Tomáš's work on...
> > >
> > > -jt
> > >
> > >
> > >
> > >
> > >
> > >
> >

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Speed of Maven build

[Jeff Jensen]

In case this helps, Jason Dillon has a "Maven Shell" that does what you
seek for CLI - launches a Maven instance and runs interactive commands with
it, saving the startup time.
https://github.com/jdillon/mvnsh


On Tue, Aug 25, 2020 at 12:27 AM Jaroslav Tulach 
wrote:

> > And it's Apache Maven, over the corner at https://maven.apache.org/ so
> > I suppose that community would be happy to get such contributions.
> >
> > -Bertrand
>
> You are right, Bertrand. Why not ask!
>
> Hello Maven guys,
> we had a discussion on the NetBeans mailing list recently and here is a
> summary:
> * Apache NetBeans IDE is delegating most of its work directly to Maven
> * Users however complain that the speed isn't great
> * One of the ideas was to launch a "zombie" instance of Maven in advance
> * then actions like build, exec or test would be faster
>
> Have you thought about something like this already? Any advices?
>
> Best regards.
> Jaroslav Tulach
> NetBeans Platform Architect
>
> ne 23. 8. 2020 v 9:06 odesílatel Jaroslav Tulach <
> jaroslav.tul...@gmail.com>
> napsal:
>
> > > I agree with others, Ant is much faster day to day. But the pom.xml has
> > > become the universal project file for Java,
> >
> > Thank you all for sharing your thoughts. I know Maven start is slower,
> but
> > I
> > learned to live with it. It is interesting to hear that some of you
> > maintain a
> > dual Ant based copy of your project metadata. Once we were trying a
> > different
> > approach:
> >
> > There is a way to speed Maven in the IDE. Launch Maven, let it read all
> > XML &
> > co. files and stop it. As soon as we need to build/run/test, wake up this
> > zombie Maven process, tell it what to do and let it continue. If the XML
> > files
> > are modified, throw the process away and initialize it again. Tomáš
> Stupka
> > implemented a prototype of this and there were no issues, as far as I
> know
> > (nobody tested it thoroughly however).
> >
> > Maybe the support is even in and there is a property to turn it on. If
> the
> > Maven startup is the biggest problem for you guys, we shall investigate
> > how to
> > turn Tomáš's work on...
> >
> > -jt
> >
> >
> >
> >
> >
> >
>