I have a program that solves problems that are very computationally intense. I divide up the work and create an NSOperation for each segment. Then I put the operations in NSOperationQueue, and start the queue. Expecting the job to take three or four hours, I go to dinner.
When I return, and look at my progress screen, I find that processing has stopped sometime about an hour into the job. My mouse events restart the job, and it later completes, about four hours later than estimated. Apparently, after a give time interval without user intervention, MAC OS just goes to sleep until some user input is detected. I mean not just screen saver, but processing shutdown. Any ideas as to how I keep my megajob running in my absence? Incidentally, sometimes the work performed by each of the operations (threads) is widely asymmetrical? Any explanations? j Jim Elliott sjameselli...@me.com 2732 NW Thurman Street, Portland, OR 97210 USA Tel. +1 (503) 481-5370 Motzstrasse 83A, 10799 Berlin, Germany +49 (30) 269-47848 +49 (179) 757-9132 _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
