Parallel build on CCS5.4

David Luca

Hello,

I have enabled in Project properties->Build->Nehaviour->Enable parallel build->Use number of processors(4) and it was building using all 4 cores just fine, CPU was 100%, but 2 days ago I've added in pre-build step a command to call an executable and since then it builds only on one core, processor load is 25% and is 3 times slower. I tried removing the pre-build step, deleting workspace and is doing the same. I can see the gmake command is "gmake -k -j 4 all".

Any idea what happened?

Z:\>echo %NUMBER_OF_PROCESSORS%
4

Best regards,

David.

over 12 years ago

0 Gautam Iyer over 12 years ago

Guru 192875 points

Hi David,

Did you try uninstalling and re-installing of CCS? This might solve your issue.

Regards,

Gautam

0 David Luca over 12 years ago in reply to Gautam Iyer

Expert 2795 points

Just tried that, it's doing the same.

Best regards,

David.

0 Gautam Iyer over 12 years ago in reply to David Luca

Guru 192875 points

Final option is to check the same on a different PC.

0 David Luca over 12 years ago in reply to Gautam Iyer

Expert 2795 points

It's the only PC I have available at the moment with these specifications. I tried a previous version and it builds using all 4.

Best regards,

David.

0 Gautam Iyer over 12 years ago in reply to David Luca

Guru 192875 points

Hard luck mate. I hope a TI employee rescues you!

Regards,

Gautam

0 David Luca over 12 years ago in reply to Gautam Iyer

Expert 2795 points

Thank you for your suggestions, they are appreciated. I'm hoping that TI employees have also seen this strange behavior.

Best regards,

David.

0 desouza over 12 years ago

TI__Guru**** 171349 points

David,

It is really odd, but I seem to be able to reproduce this.

I will have to do some additional tests to see if it is my perception or a problem with either gmake or Eclipse, but I see my pre-build step running and I also see gmake calling the four processes (-j 4), therefore it is unclear where the issue is coming from. If it is from Eclipse we may be able to fix, but if it is from gmake I am not so sure.

I'll get back to this thread after checking some additional things.

Regards,

Rafael

P.S. Eclipse CDT has a related bug filed that references the same options, therefore I wonder if it is influencing this behavior.

0 Ralf Goebel over 12 years ago in reply to desouza

Genius 3715 points

Hello,

I also see this behavior with -j 8 on CCS v5.5. If I remove the pre-build step, CCS starts using 8 cores again. What also works is using an infinite number of jobs (-j) instead.

Ralf

0 Roman Karlstetter over 12 years ago in reply to Ralf Goebel

Intellectual 560 points

I can confirm this behaviour with -j 6 as soon as I add a pre-build step on CCS v5.5. If I remove the pre-build step, the build is done using 6 parallel jobs.

When a pre-build step is active, I use an unlimited number of jobs as a workaround.

Roman

0 AartiG over 11 years ago in reply to Roman Karlstetter

TI__Guru**** 173310 points

For those following this thread or others that might hit this issue, there is now a bug report for tracking this issue so we can see if it can be fixed for a future CCS release. The tracking # is SDSCM00050659, and its status can be seen using the SDOWP link in my signature.

0 David Boles over 9 years ago in reply to AartiG

Intellectual 850 points

We have experienced the loss of parallel builds when moving from CCS 5.2 to CCS 5.5 We are using the -j 8 option but the builds have gone from 8+ minutes to 47+ minutes. Our 8 processor PC is only running under 10% CPU utilization during the build. We are not upgrading to CCS 6.x since we will lose the simulator. Can we patch the latest CCS 5.5 somehow?

0 David A. Luca over 9 years ago in reply to David Boles

Intellectual 310 points

I assume you have a pre-build step in which case try option gmake -j without a number or set to infinite number of jobs from he environment.

0 David Boles over 9 years ago in reply to David A. Luca

Intellectual 850 points

Some developers don't want to change their current build options. But we may have to do this in the end. Can we get TI to fix something that is broken?

Code Composer Studio™︎

Code Composer Studio forum

Parallel build on CCS5.4