Re: Xcode performance issues over time
Re: Xcode performance issues over time
- Subject: Re: Xcode performance issues over time
- From: Andreas Grosam <email@hidden>
- Date: Mon, 15 Feb 2010 11:41:50 +0100
On Feb 15, 2010, at 8:13 AM, Gideon King wrote:
> I have a performance issue on every build that builds more than 8 files - it says it is compiling file 8 of x files, and then stops there for about a minute, taking massive CPU (basically locks up my machine), and then continues and compiles normally. Is this normal behaviour? I expect it is something to do with getting my 8 cores loaded up and processing the compile.
>
> Gideon
Well, the information are too vague to give a definitive answer. Usually, if optimizations are off and you are compiling C, Objective-C or plain C++ (that is, no huge translation unit with tons of templates and inlines) then compiling should be pretty fast.
It may take much longer when optimization is on, especially with C++ code consisting of tons of templates and inlines. This challenges the compiler - but produces also extremely fast and tight code.
Precompiled headers give a huge performance boost - ensure, your project uses them.
However, it may be possible that there is some locking issue. Xcode can compile more than one translation unit at once - and you may attempt to edit the files, or may change project/target settings. That there are locks is reasonable, and where are locks, there is a possibility for lock contention.
There are also back ground tasks (code sense, documentation updater), which may cause performance issues. It is also possible, that code sense may be choked by invalid code, recursive included headers, or whatever. Code sense isn't very communicative when it encounters troubles - and it shouldn't. It should just terminate, clean up and retry. But it may cost performance, and it may also consume memory. And, there may be pathological cases ...
>
>
> On 15/02/2010, at 4:46 PM, Jerry Krinock wrote:
>
>> Getting back to the original topic, a few weeks ago I was waiting for a Project Find search to complete and said, "Wait a minute -- I remember last week this happened in just a few seconds". And then I realized that everything was slow -- builds took a long time, text editor could not keep up with my typing, etc.
>>
>> So, now I watch for the slowdown, and whenever I notice it, once a week or so, I close and reopen the project, or relaunch Xcode. The close/reopen is probably sufficient; not sure yet.
>>
>> It's Xcode 3.2.1. I'll file a bug if I ever figure out how to reproduce it with a demo app. I presume there's just a memory leak.
>>
>> _______________________________________________
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden