find proccess with largest rss #300
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…arlyoom into get_cmdline_while_killprocess
|
I'm curious how/when badness is not accurate. In your screenshots it seems fine:
|
rfjakob
requested changes
Sep 22, 2023
e.g: i want the process java... badness 73, VmRSS 2359MiB to be killed before gunicorn ... badness 1004, VmRSS 129 MiB |
|
rfjakob
requested changes
Oct 1, 2023
rfjakob
approved these changes
Oct 8, 2023
|
Is there any issue or concern regarding this request? |
|
No, code is ok but I need to find time to test it manually
…On Wed, 11 Oct 2023, 11:32 Ran Huang, ***@***.***> wrote:
Is there any issue or concern regarding this request?
—
Reply to this email directly, view it on GitHub
<#300 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACGA7YKK2ZTAHEAD3I242DX6ZRTLANCNFSM6AAAAAA45U3WB4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Merged, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By default, earlyoom identifies and terminates the process with the highest oom_score. However, in my Linux system, the oom_score is not an accurate indicator.
Instead, I would like to identify and terminate the process with the highest memory usage.
find process with the largest oom_score
find process with the largest rss
