• Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 1115 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Slow compile

Colin Burnell
Prodigy 20 points

Other Parts Discussed in Thread: MSP430G2553

I have CCS version 6.1.2.00015, target is MSP430G2553, compiler TI v4.4.7.

I currently have a small test project with 4 source files; I would say these contain no more than 400 lines of code in total.

A clean and build of the project takes nearly 2 minutes.

If we build the project on a colleagues machine it takes a couple of seconds; we moved the project to a network directory, and built on both machines from the same path, same results.

PC is Win7 x64, quad Zeon cores (2 threads per core); 12GB RAM, 500GB SSD HD; so not brand new, but no slouch either; and I have a couple of other compilers - Visual studio, GCC ARM, Microchip - that all run fine. Probably worth mentioning, machine also has an Eclipse Luna 4.4.1 install for Linux ARM work.

Having searched through the forum and FAQ I have tried: turning anti virus off; turning ULP advisor on/off; enabling/disabling parallel builds; uninstall, delete folder, reboot and reinstall. None have improved the situation.

Anyone have any ideas?

Thanks.

   Colin.

  • TI__Guru**** 171709 points
    Colin,

    I am pretty sure that is not the case, but I have to ask: are both hosts are actually building the project? In other words, I suppose the faster one is not simply returning from an up-to-date build attempt, right? The gmake would report the famous message gmake: Nothing to be done for `all'.

    If that is not the case, then this is a very strange one; I can see from your description that you pretty much covered most of your bases regarding the host PC itself. One detail I usually experience in my own hosts is related to network or subst drives and resources. Despite you tested the project in the network, perhaps the slower machine has other shared or PATH environment variables that point to slow networked drives, or even directories that are assigned drive letters via SUBST.

    I would also look at the workspace itself: some of my most crowded workspaces have many projects that naturally impose a performance impact in either displaying data, opening views, etc.

    One thing that I experienced as well was the use of automated backup or disk maintenance software. When these things were running on the background, especially if a mechanical hard drive is involved, can bring a computer down to its knees. In your case, given your system is running a SSD, this would be perceived as a slowdown (it happens on mine).

    Therefore my suggestions are to carefully inspect for preconfigured networked resources, running third party software and import your project to a different workspace and see if you can get some improvement.

    I will certainly reply to this thread if I can think of any additional detail.

    Hope this helps,
    Rafael
  • in reply to desouza
    Prodigy 20 points
    Desouza

    Thanks for your reply.

    Yes, we did a clean build on both machines.

    Our network paths are set by a domain script running net commands on login, so the mappings are exactly the same for both machines; plus I have same issue building locally on the SSD.

    I tried your workspace idea; I created a completely new workspace in a separate folder, and copied in just the code - .c & .h - files; no difference.

    I also disabled the Intel disk management services and rebooted the machine; again no difference.

    I am going to try uninstalling CCS again; this time I will strip CCS entries from the registry before reinstall.


    Colin.