This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS compilation delay due to strange network requests

The last few days when I try to compile my C2000 project the process takes a very long time. Although I have set the project to compile using 8 parallel jobs, I see in the console that after the 8 first jobs are started at once, the next ones take a lot of time and start once at a time.

Testing with the network connection disabled I found that the problem is gone. So I monitored the connections started by CCS and found that during compilation it makes requests to port 80 of various akamai IPs like 104.96.149.54 ! It seems rather strange, if not suspicious, that this is happening so I would like to know why is CCS making these requests every time a new compiler job is fired and what kind of information is exchanged. The fact that this "feature" also delays significantly my work is even worse, though to be fair it was the reason I looked into the problem and found about this strange behavior.


I have tried blocking CCS access to the specific IPs but this only works for a few hours or a day because the IPs change after that.

  • Giannis,

    We host our updates on Akamai to improve download speeds. The CCS will make requests to Akamai IPs as part of the update checks. I would next expect that to impact compiling.

    Can you try disabling updates to see if that makes a difference? Go to Window ->Preferences. Select Install/Update in the tree on the left and then automatic updates under that. Then on the right uncheck the box to check for updates automatically.

    Regards,
    John
  • Giannis Roussos said:
    . So I monitored the connections started by CCS and found that during compilation it makes requests to port 80 of various akamai IPs like 104.96.149.54 !

    There was a similar thread does compiler need internet connection ??, for which a suggested work-around was to try and disable the TI error parsers.

    Not sure if you are encountering the same problem, and there is no feed back on the other thread of if disabling the TI error parsers helped.

  • I would be interested to know if disabling the error parser makes a difference. That ping should be going to the wiki instead of Akamai but as Chester points out it does to to the internet.


    John