Re: Project as aggregation of other projects. Indexing disabling for such project
Re: Project as aggregation of other projects. Indexing disabling for such project
- Subject: Re: Project as aggregation of other projects. Indexing disabling for such project
- From: Joar Wingfors <email@hidden>
- Date: Mon, 02 Jan 2012 21:18:36 -0800
On 2 jan 2012, at 00:59, Ruslan Zasukhin wrote:
> On 12/27/11 5:51 PM, "Michael Rice" <email@hidden> wrote:
>
>> I thought indexing ran at a lower priority. In a similar vein, could you run
>> your app at a higher priority?
>
> It is not in low priority
>
> XCODE 4.2 have used all 99% of CPU on my i7 8 core macbook
>
> XCODE 4.2.1 was corrected to use only 50% maximum of CPU power ...
>
> And no sense move it lower, because without indexing it will not work
> correctly right?
I don't think that "low priority" necessarily means "always using less resources". It should strictly speaking only mean that the task will yield to other tasks of higher priority, but that it could still use all resources if there's nothing else of higher priority available.
That said, to properly manage the users *perception* or *expectation* of how much resources a particular task should be allowed to consume, it may still be more appropriate to cap low priority tasks.
Finally, when you have a task that's IO constrained, such as indexing, it is also not always possible / efficient to make use of all available CPU resources. In this particular case, I think that this is what you're seeing (indexing being CPU capped to avoid overcommitting on IO).
Joar
_______________________________________________
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