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: Sun, 30 Dec 2007 12:14:58 +0100
Thanks everybody for the replies so far. I think I'll have a look at
thread affinity tags first.
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.
My first guess is that you may be running into synchronization
problems with data that's shared between two threads. That's a bug in
your code and needs to be addressed by ensuring the synchronization is
correct; just reducing the number of cores available for scheduling
will probably still exhibit the problems at some time.
I am aware that something goes wrong in my code, but it's most likely
related to UI events and threads rather than data synchronization (no
crashes occur, UI just doesn't respond to mouse events on an 8-core
Mac). I haven't written all of the code myself and the project is huge
and complex, so I need to narrow down the issue incrementally.
In the future, when asking a question like this, it'll be useful to
describe what your goal is rather than just one way you think you
might be able to achieve it. That will lead to better help from the
list.
That's true. If I only knew what my goal was ;-) I have no idea so far
as to what my problem is, so the idea was just to "emulate" the dual
core environment as a temporary fix. My threads are rather light weight,
so two cores are more than enough anyway.
Thanks again.
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