On all my ARM uVision projects, browse information options increases compile time , but in a rationally way. Today , I imported a colleague project to fork it. And it was a disaster !
Without 'Browse information' activated : 40s to compile all files (without link) With the option activated : 9.07 min !! So a time factor of 13.7 !! it's insane! First I thought about the AV software , but it's still the same with AV deactivated. I looked deeply in what could be the cause of such a difference. And the only thing I can see is the structure of the project , with a lot a C small modules rather than small number of big files... The CRF files has 2/3 to twice the other projects size. But it seems that the impact on the compilation time is exponential and not linear.
I'm using uvision 4.74. If i'm trying with the last uvision version (5.16a) that can manage multi core compilation , it's getting worse... This time my mouse is unusable during the compilation time with a lot of lags ...
Seriously , Keil could learn from eclipse. Whatever the project (at least mines) , the index is created in max 5s for the complete project...
Works well for me. Conclusion: Something wrong with your machine or the configuration.
You should seriously consider a course to increase your understanding.
first it's reproducible on another machines. Secondly , the fact that it's working well (and it's magical you have the same project structure than me !! ) does not mean it's working in all cases. And finally, Thank you so much for sharing your innate knowledge.
Then I suggest you send us your project so we can prove the problem either way. Without that, how can anybody take your complaint seriously?
I've been using 4.74 for a very long time with very many projects of various sizes. Speed has never been an issue. It looks like your one project is in a very low percentage of failures.
But we have a policy of ensuring the machines used for development are well configured. Do you?
Really , send you the project ? I guess you'll have to sign a NDA , or I'll have to kill you after :) What happens is exactly what I said . The reason of why , however , It's just a guess, and observations I can make.
I can reproduce the problem on 3 different machines at work. Tonight I'll test on my own computer at home , running on a different OS, other hardware config and so on.
I'm pretty sure it's due to a particular thing in the project, not the machine.
What does task manager show?
Just high CPU load during this time or does something happen with consumed memory? Disk swapping?
Normally, a Windows machine should not get issues with the mouse unless it is busy doing low level stuff that makes it lock up synchronization objects deep down in the kernel. Heavy swapping is another situation where the mouse cursor may start to misbehave. But it sounds like your machine for some reason really is in pain during the build.
the mouse lag only occurs with uVisdion V5. So for now, i'm trying to focus on the V4 (and the project was created with V4).
ArMcc.exe is at 13% cpu max on one core (on a total of 8) Free RAM is about 3.6GB on 8GB. Max rate of files written by armcc is 600KB/s
Concerning the SWAP file , The size is managed by Windows. the current size is 8GB. My HD is a Samsung SSD.