IIRC Java still defines the workspace locking rule, hence its build cannot run in parallel. For PDE I think Mickael enabled parallel builds via https://bugs.eclipse.org/bugs/show_bug.cgi?id=531555
For JDT I think the work is discussed in https://bugs.eclipse.org/bugs/show_bug.cgi?id=531554 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=527212 On Wed, Jan 27, 2021 at 10:44 AM Alex Blewitt <alex.blew...@gmail.com> wrote: > IIRC the parallel builds works if you have independent projects. So if you > have B->A and C->A, then you can build A, then build B&C in parallel. > > If you have C->B->A then there won’t be any parallelisation. > > ISTR that B is blocked until A is built completely, even if parts of B > could go ahead from a pure Java perspective, because we build projects in > atomic units. > > Alex > > Sent from my iPhone 📱 > > On 22 Jan 2021, at 12:34, Wim Jongman <wim.jong...@gmail.com> wrote: > > > Cool. > > I am new to this too. I have activated it (set to 5 (5 jobs?). But a full > java build takes just as long and I do not see multiple build jobs. > > I have a 270 project workspace. For normal 99% work, the incremental build > is working fine. It is slow (or rather, it takes a long time) when a full > rebuild needs to take place, which is somewhat annoying. It occurs mostly > when adding/removing dependencies. > > > > On Fri, Jan 22, 2021 at 1:25 PM Mickael Istria <mist...@redhat.com> wrote: > >> On Fri, Jan 22, 2021 at 1:04 PM Alex Blewitt <alex.blew...@gmail.com> >> wrote: >> >>> Can we update the default to ‘true’ or ‘max processors’ or ‘half >>> processors’ or similar, so we can enable it out of the box for every >>> project build type? If not, what’s stoppping us from doing so? >>> >> >> When this feature was introduced some years ago, there were some >> communication about it asking for people to try it and give feedback. Based >> on this feedback, we could then decide to change default or not. We didn't >> receive any substantial feedback and my first impression back then is that >> because JDT being a bit greedy in scheduling rules, changing default in the >> IDE didn't make a difference back then. So it has remained as it. >> If enough people are willing to try it in their workspace, verify it >> works as expected, that it creates a performance gain, report any bug they >> face; then we could decide to change the default based on that feedback. >> _______________________________________________ >> platform-dev mailing list >> platform-dev@eclipse.org >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/platform-dev >> > _______________________________________________ > platform-dev mailing list > platform-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/platform-dev > > _______________________________________________ > platform-dev mailing list > platform-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/platform-dev > -- Eclipse Platform project co-lead CEO vogella GmbH Haindaalwisch 17a, 22395 Hamburg Amtsgericht Hamburg: HRB 127058 Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel USt-IdNr.: DE284122352 Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com
_______________________________________________ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
