> "Currently our approach for scheduling is that apps doing background work on > a thread should lower that thread's priority"
Whoops. I released an app that didn't do this. It's not obvious, I think. > We are looking at more strongly enforcing that background applications can > not take too many cycles from the foreground. I thought service threads were already niced down. The kernel scheduler doesn't use nice priorities effectively? The timeslices are too large? Is this a problem because the game expects to be able to peg the cpu for minutes or hours at a time? I don't think that's a realistic expectation. There's no magic scheduling change that can fix that assumption - if your app cannot tolerate losing the cpu for brief periods of time, it isn't suitable for a multi-tasking OS! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
