Re: Detecting non-responsive app
Re: Detecting non-responsive app
- Subject: Re: Detecting non-responsive app
- From: Bill Bumgarner <email@hidden>
- Date: Sat, 26 Aug 2006 12:33:01 -0700
On Aug 25, 2006, at 10:54 PM, Drew McCormack wrote:
Why do I need this? I have an app that wants to do things in the
user's 'dead time' (not the computers), and this is one time I
thought the user could be sitting and waiting. (If you have any
other times that the user is likely to be waiting, I welcome all
suggestions.)
That won't work.
First, the SPOD'ing app may not be the foreground app. Secondly,
well engineered apps should never SPOD. If they do SPOD, it may
indicate that there is a more serious underlying problem, often
network resource related (Network filesystems being unavailable
immediately and painfully comes to mind).
If you want your app to run at the least intrusive times, have a look
at the "nice" man page. The kernel has facilities for adjusting the
scheduling of an app.
However, this isn't entirely adequate in that things such as memory
pressure or I/O issues may cause additional load and/or problems that
pure CPU scheduling can't deal with.
b.bum
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden