|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.
Sent from my iPhone 📱
On 22 Jan 2021, at 12:34, Wim Jongman <wim.jongman@xxxxxxxxx> wrote:
I am new to this too. I have activated
(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.
_______________________________________________platform-dev mailing listplatform-dev@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
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
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev