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

Reply via email to