On 01/04/2014 14:20, Thinker K.F. Li wrote: > We bind LMK parameters and priority to the fact of foreground or > background. A foreground app get more likely to survey while the apps > running out the memory. The problem is while an app is launched, it is > in background at beginning, and go to foreground later. It means the > existing foreground does not go to background immediately.
Could you elaborate a bit on this? With "going to the foreground/background" do you mean the moment when the LMK & nice parameters are set or just when we switch the app visibility? > I am not sure if making a just launched app as the foreground > immediately would break anything!? Or, we should lower the priority of > the existing foreground app temporary!? In general when launching an app it will start from the pre-allocated process which is considered in the background (although it now has its special LMK class) so we'll be always starting from the background anyway. Is something significant going on in the preallocated app before it's nice value / LMK parameters are adjusted or is it happening before it becomes visible? IIRC we first make the app window visible and only afterwards set its nice / LMK parameters so there might be room for improvement there. Gabriele
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
