Hi
Ki-Soo Lee said:That is a beast of a machine, blows away anything I have used. No way it should take 4 minutes to get started
I thought it was a beast until it met Godzilla (aka CCSv6 )
Could it be that the slowness has got to do with the number of .c and .h files in my project that eclipse parses when trying to create editor symbolic links? (like linking to a declaration and definitions to function calls)
Ki-Soo Lee said:If you close the project, it should not parse/scan it.
But if I close the platform configuration, then it won't get linked when I build my application right? (update: my app won't build without the platform config project open).
I noticed that its stating "Invoking scanner config builder on project M2_EVM6472" even when I save a file. What pops up is the window below. Can I turn off the auto config builder somehow?
Also, is there a way to get it to do an incremental build instead of a clean build each time? Hopefully I can find where this setting is. I don't think I had to play with it in CCSv4.
Hi Baltasar
Its definitely the project because CCSv6 is up in a flash (relatively speaking) with other workspaces I've created.
Unfortunately I can't share the project since its production code. But anything else I can capture for you, i.e. logs etc, I'll gladly do because this is really slowing down our team. (and I'm the main scapegoat since I suggested we migrate to CCSv6).
I used Process Explorer to monitor that CPU loading while "Invoking Configuration Builder" is running and its hardly using any MIPs (less than 4% CPU load). So I can't understand why it takes so long.
I noticed that it says its "Migrating Legacy Project". Perhaps something is not being written back correctly to one of CCSv6's config files that tells it that the project has been converted?
Cheers
Hi Desouza
Glad you have given me some things to try.
desouza said:What happens if you close (right-click --> Close Project)
Surprisingly, its not the referenced platform thats causing the problem. Its our project. I suspect its because the project has some 430 files.
desouza said:How large is the source file that is being continuously accessed?
I don't think its one file. Please see some of the Process Monitor files I uploaded. The "Refreshing Paths and Symbols" activity is creating over 600,000 events that are mostly file open and close in the compiler path. Below is the Process Monitor detail on the open event. It doesn't say what while its opening, but I can post the raw Process Monitor output so you can peruse the event details.
desouza said:Since I mentioned the Indexer, do you still face this with the Indexer disabled? (
I turned off the indexer and no difference. When I unchecked the box and then clicked "apply", the Refreshing Paths and Symbols" activity started its never ending assalt on the file system.
desouza said:You can also disable the Indexer for the project only
I couldn't find this feature, but it would be handy if I thought it was the indexer. But the previous experiment suggest its not.
desouza said:Perhaps the heap garbage collection is getting in the way. Can you increase the heap usage as mentioned
I increased it to 1024. Still no improvement. :o(
The other two engineers in our group are having the same issue as I am experiencing - the refreshing paths and symbols is taking a mightly long time, even when you save a file.
Keep the ideas comin!
Cheers
Thanks but 6.2 does exactly the same thing, it takes over 5 minutes to rebuild a simple 1 file example, with long period of blocked and waiting. So that did not solve the issue. This has been around now a long time and actually makes code development unbearable. Yes I no longer expect much in the tool chain from TI since the move to Eclipse but there are limits. Any other suggestions?
