It would be really good to get a post in the Android blog regarding this.I found out about the thread priority when coding my activity.
My twitter app allows you to read stored tweets while it gets the new ones + pictures on background. It was scrolling really bad (like SlideMe) until I modified the thread. I'm not SO sure that made the difference but I can feel it scrolls better. Ivan Soto Fernandez Web Developer http://ivansotof.com On Fri, Mar 27, 2009 at 10:03 AM, Mike Hearn <mh.in.engl...@gmail.com>wrote: > > > "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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
