improve chrome tab and android app discard under memory pressure |
|||||||||||
Issue descriptionThis meta-bug covers several issues: 1. Order of discards. We think that there are cases in which the discard order in a mixed Chrome/Android environment is far from optimal. 2. Pressure at discard. We often see excessive performance degradation, likely due to too much work in the kernel memory manager, before a discard occurs. 3. Discard vs. OOM kills. The system was tuned to use discards to prevent the kernel from making OOM kills. Some OOM kills are unavoidable but should be minimized. According to UMA stats, some platforms see a majority of discards, others see a majority of OOM kills, and we should fix the latter. 4. Priority of OOM kills. The current setup does not guarantee that processes are OOM-killed in the same order in which tabs are discarded. In general this guarantee cannot be achieved because tabs may be discarded without killing the underlying renderer, which may be serving multiple tabs. Next, I'll find or open bugs for each of these points and link them here. ⛆ |
|
|
,
Mar 16 2017
This bug is NOT for generic linux memory manager misbehavior such as issue 645198. Here we try to work around what we have. Also this bug is NOT for keeping track of memory leaks such as crosbug.com/p/62731.
,
Mar 16 2017
Blocking on bug 701848 which addresses point 4: kernel OOM kill priority is not the same as tab/app discard priority.
,
Mar 16 2017
For the reader: issue 645512 is a related mega-bug with many discussions and experiments.
,
Mar 16 2017
Blocking on issue 702275: order of tab discards/android app kills may be suboptimal (to address point 1).
,
Mar 16 2017
Blocking on issue 702282: tune/improve low-memory threshold calculation (addressing point 2)
,
Mar 16 2017
Actually issue 702282 addresses point 3 as well. They kind of go together.
,
Apr 4 2017
,
Apr 6 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned". |
||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by puneetster@chromium.org
, Mar 16 2017Status: Available (was: Untriaged)