CCS/CCSTUDIO: Slow Compilation behind firewall

Stefan Haensel

Part Number: CCSTUDIO

Tool/software: Code Composer Studio

Hi,

I'm working at a big company, which has some firewall settings, I cannot change.

Sins few month I have the problem that compiling a project takes like 10 times of the normal time.
When I switch of my internet connection it gets fast again.
I read some stuff and I believe, that CCS checks some TI server, which are not available though the firewall, but since there is a internet connection, it runs into a really long timeout.
When I switch off the connection, it doesn't try to connect or gets the timeout directly.

I read, that CCS tries to get more information about compiling errors. Is it that, what CCS makes it incredible slow?

I tried to use my own firewall settings to disconnect CCS from the internet, but without any success.

Is there anything I can do?

Best Regards,

Stefan

over 5 years ago

0 AartiG over 5 years ago

TI__Guru**** 173310 points

Stefan,

There was a similar issue reported here (appears to be from the same company). I suspect your issue might be due to the same root cause (slowdown due to cmd.exe). You could verify if that is case by disabling makefile auto-generation and removing the lines from the makefile that set the shell to cmd.exe, as described in that thread.

If that ends up being the root cause then you would need to talk to your company IT department to see why that is happening when on company network.

0 Stefan Haensel over 5 years ago in reply to AartiG

Intellectual 680 points

Yes. Same problem, same company.

Thank you

0 Stefan Haensel over 5 years ago in reply to Stefan Haensel

Intellectual 680 points

Now I figured out the problem and how to solve it:
(Thanks to Wireshark :) )

during startup and compilation CCS tries to connect to a server hosted on Akamai. It looks like, our Firewall blocks this without any response. So CCS or cmd waits until a timeout is reached.

To solve this an entry in the widows hosts (C:\Windows\System32\drivers\etc\hosts) file is enough:
0.0.0.0 osce11-en.grid-gfr.trendmicro.com

This redirects the question on the Akamai server to nowhere. And compilation gets fast again!

Maybe you guys from TI can say something about that. Why you need this server during compilation? What are you trying to sent to this server?
Can you also link this answer to the following treat?
e2e.ti.com/.../701209

0 JohnS over 5 years ago in reply to Stefan Haensel

TI__Guru**** 159715 points

Stefan,

We host our downloads on Akamai. I don't know why we would be pinging Akamai during a build. The only thing I can think of is that somehow an update check is getting caught up in the build. By default we do an update check in the background when you start CCS. This would be accessing Akamai. It is possible to disable the update check in the preferences dialog here:

We are going to continue to look into this.

Regards,

John

0 W Lai over 5 years ago in reply to JohnS

TI__Prodigy 670 points

Hi Stefan,

Can you add the attached 'compiler_specs.txt' file into your 'ccsv8\eclipse\configuration\com.ti.ccstudio.errorparser' directory?

This will make ccs build NOT to connect to the server during ccs build.

Please let me know whether it helps.

7607.compiler_specs.txt

2533656291388
http://processors.wiki.ti.com/index.php/Compiler
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/#mw-head
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/#p-search
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/C6000
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/10099
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/10198
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/10202
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/10234
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/16000
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/16008
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/17003
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/225
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/27007
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/27008
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/27009
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/27010
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/27011
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/5
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/994
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/C6000
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/C6000/27000
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/C6000/27001
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/C6000/27002
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/C6000/27003
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/C6000/27004
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/C6000/30000
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/C6000/30001
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/C6000/30002
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/C6000/30003
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/C6000/30004
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/C6000/30005
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/C6000/30006
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/C6000/30007
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/C6000/30008
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/C6000/30009
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/C6000/30010
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/C6000/30011
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/10030
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/10371
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/10372
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/10374
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/10420
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/10421
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/10422
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/10424
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/10436
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1521
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1527
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1528
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1530
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1531
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1532
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1533
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1534
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1535
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1536
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1537
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1538
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1539
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1540
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1541
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1542
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1543
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1544
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1545
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/MSP430/1546
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/internal_error
http://processors.wiki.ti.com/index.php/File:E2e.jpg
http://e2e.ti.com
http://processors.wiki.ti.com/index.php/File:Hyperlink_blue.png
http://www.ti.com/lsds/ti/analog/amplifier_and_linear.page
http://www.ti.com/lsds/ti/analog/audio/audio_overview.page
http://www.ti.com/lsds/ti/analog/rfif.page
http://www.ti.com/lsds/ti/analog/clocksandtimers/clocks_and_timers.page
http://www.ti.com/lsds/ti/analog/dataconverters/data_converter.page
http://www.ti.com/lsds/ti/analog/mems/mems.page
http://www.ti.com/lsds/ti/analog/high_reliability.page
http://www.ti.com/lsds/ti/analog/interface/interface.page
http://www.ti.com/lsds/ti/logic/home_overview.page
http://www.ti.com/lsds/ti/analog/powermanagement/power_portal.page
http://www.ti.com/lsds/ti/dsp/embedded_processor.page
http://www.ti.com/lsds/ti/dsp/arm.page
http://www.ti.com/lsds/ti/dsp/home.page
http://www.ti.com/lsds/ti/microcontroller/home.page
http://www.ti.com/lsds/ti/omap-applications-processors/the-omap-experience.page
http://www.ti.com/lsds/ti/analog/switches_and_multiplexers.page
http://www.ti.com/lsds/ti/analog/temperature_sensor.page
http://focus.ti.com/wireless/docs/wirelessoverview.tsp?familyId=2003&sectionId=646&tabId=2735
http://processors.wiki.ti.com/index.php?title=Compiler/diagnostic_messages/&oldid=213990
http://processors.wiki.ti.com/index.php?title=Special:UserLogin&returnto=Compiler%2Fdiagnostic+messages%2F
http://processors.wiki.ti.com/index.php/Special:RequestAccount
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/
http://processors.wiki.ti.com/index.php?title=Talk:Compiler/diagnostic_messages/&action=edit&redlink=1
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/#
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/
http://processors.wiki.ti.com/index.php?title=Compiler/diagnostic_messages/&action=edit
http://processors.wiki.ti.com/index.php?title=Compiler/diagnostic_messages/&action=history
http://processors.wiki.ti.com/index.php/Compiler/diagnostic_messages/#
http://processors.wiki.ti.com/index.php/Main_Page
http://processors.wiki.ti.com/index.php/Main_Page
http://processors.wiki.ti.com/index.php/Special:AllPages
http://processors.wiki.ti.com/index.php/Special:Categories
http://processors.wiki.ti.com/index.php/Special:RecentChanges
http://processors.wiki.ti.com/index.php/Special:Random
https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents
http://processors.wiki.ti.com/index.php?title=Special:Book&bookcmd=book_creator&referer=Compiler%2Fdiagnostic+messages%2F
http://processors.wiki.ti.com/index.php?title=Special:Book&bookcmd=render_article&arttitle=Compiler%2Fdiagnostic+messages%2F&oldid=213990&writer=rl
http://processors.wiki.ti.com/index.php?title=Compiler/diagnostic_messages/&printable=yes
http://processors.wiki.ti.com/index.php/Special:WhatLinksHere/Compiler/diagnostic_messages/
http://processors.wiki.ti.com/index.php/Special:RecentChangesLinked/Compiler/diagnostic_messages/
http://processors.wiki.ti.com/index.php/Special:SpecialPages
http://processors.wiki.ti.com/index.php?title=Compiler/diagnostic_messages/&oldid=213990
http://processors.wiki.ti.com/index.php?title=Compiler/diagnostic_messages/&action=info
http://creativecommons.org/licenses/by-sa/3.0/
http://processors.wiki.ti.com/index.php/Project:Privacy_policy
http://processors.wiki.ti.com/index.php/Project:About
http://processors.wiki.ti.com/index.php/Project:General_disclaimer
http://processors.wiki.ti.com/index.php/Project:Terms_of_Service
http://creativecommons.org/licenses/by-sa/3.0/
http://www.mediawiki.org/

0 Gabor Hencz22 over 5 years ago in reply to Stefan Haensel

Prodigy 80 points

Hi! I am the poster of the other thread with the same issue. I am glad you made some progress.

However, I think you misinterpreted the data seen on wireshark. I can confirm that during the build, some process is constantly accessing the trendmicro servers (in my case, it is osce12-en.grid-gfr.trendmicro.com). This happens on any network, if the PC is connected. The slowdown might be caused by the fact that in the company network, the connection is made through an HTTP proxy, which makes the process noticeably slower. In my case the firewall clearly does not block the connection.

Now I can declare for sure this is not a CCS issue. The culprit seems to be the process named "Trend Micro Common Client Real-time Scan Service". Using the task manager I could kill the process on my win10 machine and the connections to the server mentioned above ceased. Also the build became noticeably faster.

Some statistics for the build time of the same project in different circumstances:

Real time scan on:

No network: 49 seconds

Regular network: 40 seconds

Siemens network: 2 minutes

Real-time scan killed: 29 seconds. Most probably this is still not real speed achievable by a "clean" machine because an other Trend Micro process, the "Trend micro unauthorized change prevention service" cannot be killed by the regular user and it takes 25-30% CPU time during the build.

Editing the windows hosts file did not work for me. Sadly, I can not advise any easy workaround as disabling the AV is a no-go in the corporate environment.

It might be worth investing the time and setting up CCS in a (linux-based) virtual machine. On my machine building the same project under the VM took an astonishing 15 seconds!.

0 Stefan Haensel over 5 years ago in reply to Gabor Hencz22

Intellectual 680 points

Hi Gabor Hencz22,

this makes sense to me! Thank you for your description.

I thought, I know trend Micro from somewhere, but I wasn't aware, that it is our AV. This changes everything.

I still work on a win7 machine and I will talk to my IT guy, if blocking the trendmicro site is allowed. But I think it isn't.

My IT guy also found the following article. Maybe this helps for you. It didn't for me.

Trend Micro Performance Issues on Atos managed endpoints - Temporary Exception List

Best Regards

Code Composer Studio™︎

Code Composer Studio forum

CCS/CCSTUDIO: Slow Compilation behind firewall