CCS: Slow compile on some PC with CCS8 and CCS9

Hello Sheldon,
assuming a comparable h/w performance on all PCs
I would start with checking -Xmx parameter within ccstudio.ini file.
-Xmx determines jvm heap size for eclipse.
CCS900 is first 64 bit version and heap size can exeed 2 GB.
For CCS 9xx check -Xmx2048m. Older CCS versions have to have -Xmx below 2048 MB.
To monitor CCS java heap usage set it on using Window -> Preferences -> General -> "Show heap status" check box.

A long workbench history and free disk space checking are important CCS performance factors.

Sheldon He said:

Compare to some other computers which is much longer (same code generation tools) Could you give me any advise or setting to check to improve the performance?

The other computers that the customer is comparing against - is it on the same network? Are the specs of the computers the same? Also have the check their parallel builds setting: http://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_project-management.html#parallel-builds

Thanks

ki

Hi Ki and Tom,
I will give your comments to my customer. They are using workstation so generally a too slow build should have some problem.
They find one interesting thing that CPU usage in the "slow build machine" is always less than 10%.
BTW, I have let them disconnect from any network to have a try. This make no difference with the "slow build machine" in rebuild operation.
I will get back to you once I get more information from my customer.
Thanks!
Sheldon

Hi Tom,

They have had value as 768, after they changed to 4096 nothing improves. Do you have any comments?

Thanks

Sheldon

Hello Sheldon,

what memory usage the CCS java heap monitor shows?
4 GB allocation is much to high, probably. 

Do they use parallel builds on slow PCs?
Do they have HDD or SSD?

Sheldon He said:

They have had value as 768, after they changed to 4096 nothing improves. Do you have any comments?

There is a recommended value that varies per PC. On CCSv8, you don't want to go higher that 1024m. On CCSv9, you have more room but you likely don't need to go over 2048m

Did the customer check their parallel build setting? 

Ki, 

some time ago I did an experiment with CC13x2_26x2 SDK v3_10_00_53 which contains 2000+ project examples.
I did clean all and build all projects at once. 

Under CCS v901, 4096 MB for the java heap was just enough. 
Under CCS v830, 1920 MB was to less.

C/C++ indexer has huge appetite for the heap. 

In case of Linux projects involving huge libs like Qt, the java heap may need 4 GB or even more. 

Tomasz Kocon said:

some time ago I did an experiment with CC13x2_26x2 SDK v3_10_00_53 which contains 2000+ project examples.
I did clean all and build all projects at once. 

woah. 

Tomasz Kocon said:

Under CCS v830, 1920 MB was to less.

You may be ok building, but you will likely run into some issues when debugging

Tomasz Kocon said:

Under CCS v901, 4096 MB for the java heap was just enough. 

Since v9 is a 64-bit application, you have more flexibility with the max heap size. 4K is pretty big but if you have the RAM, I guess it is fine.

Tomasz Kocon said:

C/C++ indexer has huge appetite for the heap. 

yes, indeed. If you have that many open projects of that size in the same workspace, the indexer will be consuming a lot of resources.

ki 

Hi Sheldon,

Just want to follow up to see if the customer is still experiencing the slowdown during build

Thanks

ki