Re: How to limit number of CPU cores used by a Cocoa app
Re: How to limit number of CPU cores used by a Cocoa app
- Subject: Re: How to limit number of CPU cores used by a Cocoa app
- From: Andre Schnoor <email@hidden>
- Date: Sat, 05 Jan 2008 13:02:57 +0100
Dave Camp wrote:
On Dec 30, 2007, at 3:14 AM, Andre Schnoor wrote:
Chris Hanson wrote:
Why do you think restricting threads to run on only 2 cores will be
useful?
I observed problems with GUI threads when running the app on an
8-core Mac Pro, while it runs fine on dual core CPUs and PPC. The
fix is intented as a temporary workaround only until I found the real
cause.
That's your problem. All of your GUI (with a few exceptions) needs to
be on the main thread.
I understand. But why is the method that forks a drawing thread called
#detachDrawingThread:toTarget:withObject: in the first place? IMHO, this
is misleading.
If the detached thread (which currently initiates all of my graphics
output, except window and menu creation) is not allowed to do any UI
drawing, then it should not be called a "drawing" thread. Apple should
mention this in the documentation clearly.
Andre
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden