FWIW you can't always be sure that NSOperationQueue will be using a
thread per operation. The number of active operations (I explicitly
don't say "threads" here) depends on system contention. Are your
operations dependent on each other or using shared resources? Are you
setting -[NSOperationQueue maxConcurrentOperationCount:] ? If each
operation is independent then simply throw as many as you like at the
queue without setting the maxConcurrentOperationCount.
You may even find that NSOperationQueue/NSOperation allows you to
split up your calculations into smaller chunks than 1 per CPU (or
effective cores).
Can you post some example code that can shed some more light on what
you're doing?
Jonathan
http://madebysofa.com
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
