Merge lp:~thomas-voss/unity-mir/less-aggressive-scores into lp:unity-mir
Proposed by
Thomas Voß
Status: | Merged |
---|---|
Approved by: | Gerry Boland |
Approved revision: | 131 |
Merged at revision: | 134 |
Proposed branch: | lp:~thomas-voss/unity-mir/less-aggressive-scores |
Merge into: | lp:unity-mir |
Diff against target: |
139 lines (+64/-9) 1 file modified
src/modules/Unity/Application/taskcontroller.cpp (+64/-9) |
To merge this branch: | bzr merge lp:~thomas-voss/unity-mir/less-aggressive-scores |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Gerry Boland (community) | Approve | ||
PS Jenkins bot (community) | continuous-integration | Approve | |
Review via email:
|
Commit message
Ensure that app processes are not assigned an oom score smaller than the one of the shell.
Description of the change
Ensure that app processes are not assigned an oom score smaller than the one of the shell.
To post a comment you must log in.
I'd like to suggest two possible improvements:
1)
I think we want the active / front app to be scored less favorably than shell; shell is currently score -10, but I think we should score all apps positively; so I think all apps we track should e.g. start with 10, and get e.g. 800 when they get in the background, then back to 10 if they get in front etc.
-10 would be same score as current shell/session, and I think we prefer the front app to die rather than the shell.
2) could we perhaps use relative percentage scores in the code? e.g. set the mostLikelyToGet Killed to score 80% of range:
((maxValue() - minValue()) * 80 / 100) + minValue()
in fact this would ideally be computed against score of driving process (unity8) vs. max