HTOP shows massive memory usage but proceslist shows otherwise
I'm running htop on my Ubuntu 16.04LTS server to monitor my CPU and RAM usage. I'm aware of the color indications used by htop as outlined below:
So, when I look at my htop-overview, it shows me the following:
However, this seems rather unclear to me. htop shows a memory usage of almost 100% (some cached memory, but mainly used RAM). However, when I look at the main processes (childs are hidden), I won't even come close to 50% RAM usage (16.1% + 11.6% + 2.7%).
So, this confuses me a bit and I would like to know why htop shows me a almost fully used RAM-bar?
Important to note is that, looking at the meminfo page, I see the following overview, indicating a lot of cached RAM in contradiction to what htop is showing me?
So, I would actually expect a RAM-usage bar in htop with a lot more yellow/orange? Though, it consists of green for approximately 85%?
Could it perhaps be that there are many (very short running) processes, which require a lot of RAM but suspend to quickly for htop to show them?
EDIT
Another picture of htop (with processes using more memory) and meminfo together
ubuntu memory performance htop
asked Dec 22 '18 at 17:00
Thomas van Hesteren
162
|
show 1 more comment
I'm running htop on my Ubuntu 16.04LTS server to monitor my CPU and RAM usage. I'm aware of the color indications used by htop as outlined below:
So, when I look at my htop-overview, it shows me the following:
However, this seems rather unclear to me. htop shows a memory usage of almost 100% (some cached memory, but mainly used RAM). However, when I look at the main processes (childs are hidden), I won't even come close to 50% RAM usage (16.1% + 11.6% + 2.7%).
So, this confuses me a bit and I would like to know why htop shows me a almost fully used RAM-bar?
Important to note is that, looking at the meminfo page, I see the following overview, indicating a lot of cached RAM in contradiction to what htop is showing me?
So, I would actually expect a RAM-usage bar in htop with a lot more yellow/orange? Though, it consists of green for approximately 85%?
Could it perhaps be that there are many (very short running) processes, which require a lot of RAM but suspend to quickly for htop to show them?
EDIT
Another picture of htop (with processes using more memory) and meminfo together
ubuntu memory performance htop
asked Dec 22 '18 at 17:00
Thomas van Hesteren
162
Are you perhaps using ZFS?
– Daniel B
Dec 22 '18 at 17:11
@DanielB no, not that I'm aware of. Where can I check this?
– Thomas van Hesteren
Dec 22 '18 at 17:13
You’d know. On second thought, the memory usage pattern doesn’t match anyway. You have a lot of shared memory, also note how your cached memory is not considered “available”.
– Daniel B
Dec 22 '18 at 17:18
@DanielB, indeed. However, why is htop now showing it in the RAM-bar as orange/yellow since it is cached? Besides, my memory usage doesn't seem to look bad (server response is fast and good). Though, when based on htop, I would conclude that my server is used at almost 100% RAM capacity? I don't understand the relation between both
– Thomas van Hesteren
Dec 22 '18 at 17:21
Because it is not cached in the sense of being available for reuse. Something is still using this memory.
– Daniel B
Dec 22 '18 at 17:28
|
show 1 more comment
I'm running htop on my Ubuntu 16.04LTS server to monitor my CPU and RAM usage. I'm aware of the color indications used by htop as outlined below:
So, when I look at my htop-overview, it shows me the following:
However, this seems rather unclear to me. htop shows a memory usage of almost 100% (some cached memory, but mainly used RAM). However, when I look at the main processes (childs are hidden), I won't even come close to 50% RAM usage (16.1% + 11.6% + 2.7%).
So, this confuses me a bit and I would like to know why htop shows me a almost fully used RAM-bar?
Important to note is that, looking at the meminfo page, I see the following overview, indicating a lot of cached RAM in contradiction to what htop is showing me?
So, I would actually expect a RAM-usage bar in htop with a lot more yellow/orange? Though, it consists of green for approximately 85%?
Could it perhaps be that there are many (very short running) processes, which require a lot of RAM but suspend to quickly for htop to show them?
EDIT
Another picture of htop (with processes using more memory) and meminfo together
ubuntu memory performance htop
asked Dec 22 '18 at 17:00
Thomas van Hesteren
162
I'm running htop on my Ubuntu 16.04LTS server to monitor my CPU and RAM usage. I'm aware of the color indications used by htop as outlined below:
So, when I look at my htop-overview, it shows me the following:
However, this seems rather unclear to me. htop shows a memory usage of almost 100% (some cached memory, but mainly used RAM). However, when I look at the main processes (childs are hidden), I won't even come close to 50% RAM usage (16.1% + 11.6% + 2.7%).
So, this confuses me a bit and I would like to know why htop shows me a almost fully used RAM-bar?
Important to note is that, looking at the meminfo page, I see the following overview, indicating a lot of cached RAM in contradiction to what htop is showing me?
So, I would actually expect a RAM-usage bar in htop with a lot more yellow/orange? Though, it consists of green for approximately 85%?
Could it perhaps be that there are many (very short running) processes, which require a lot of RAM but suspend to quickly for htop to show them?
EDIT
Another picture of htop (with processes using more memory) and meminfo together
ubuntu memory performance htop
ubuntu memory performance htop
asked Dec 22 '18 at 17:00
Thomas van Hesteren
162
asked Dec 22 '18 at 17:00
Thomas van Hesteren
162
edited Dec 22 '18 at 17:32
asked Dec 22 '18 at 17:00
Thomas van Hesteren
162
asked Dec 22 '18 at 17:00
Thomas van Hesteren
162
asked Dec 22 '18 at 17:00
Thomas van Hesteren
162
162
Are you perhaps using ZFS?
– Daniel B
Dec 22 '18 at 17:11
@DanielB no, not that I'm aware of. Where can I check this?
– Thomas van Hesteren
Dec 22 '18 at 17:13
You’d know. On second thought, the memory usage pattern doesn’t match anyway. You have a lot of shared memory, also note how your cached memory is not considered “available”.
– Daniel B
Dec 22 '18 at 17:18
@DanielB, indeed. However, why is htop now showing it in the RAM-bar as orange/yellow since it is cached? Besides, my memory usage doesn't seem to look bad (server response is fast and good). Though, when based on htop, I would conclude that my server is used at almost 100% RAM capacity? I don't understand the relation between both
– Thomas van Hesteren
Dec 22 '18 at 17:21
Because it is not cached in the sense of being available for reuse. Something is still using this memory.
– Daniel B
Dec 22 '18 at 17:28
|
show 1 more comment
Are you perhaps using ZFS?
– Daniel B
Dec 22 '18 at 17:11
@DanielB no, not that I'm aware of. Where can I check this?
– Thomas van Hesteren
Dec 22 '18 at 17:13
You’d know. On second thought, the memory usage pattern doesn’t match anyway. You have a lot of shared memory, also note how your cached memory is not considered “available”.
– Daniel B
Dec 22 '18 at 17:18
@DanielB, indeed. However, why is htop now showing it in the RAM-bar as orange/yellow since it is cached? Besides, my memory usage doesn't seem to look bad (server response is fast and good). Though, when based on htop, I would conclude that my server is used at almost 100% RAM capacity? I don't understand the relation between both
– Thomas van Hesteren
Dec 22 '18 at 17:21
Because it is not cached in the sense of being available for reuse. Something is still using this memory.
– Daniel B
Dec 22 '18 at 17:28
Are you perhaps using ZFS?
– Daniel B
Dec 22 '18 at 17:11
Are you perhaps using ZFS?
– Daniel B
Dec 22 '18 at 17:11
@DanielB no, not that I'm aware of. Where can I check this?
– Thomas van Hesteren
Dec 22 '18 at 17:13
@DanielB no, not that I'm aware of. Where can I check this?
– Thomas van Hesteren
Dec 22 '18 at 17:13
You’d know. On second thought, the memory usage pattern doesn’t match anyway. You have a lot of shared memory, also note how your cached memory is not considered “available”.
– Daniel B
Dec 22 '18 at 17:18
You’d know. On second thought, the memory usage pattern doesn’t match anyway. You have a lot of shared memory, also note how your cached memory is not considered “available”.
– Daniel B
Dec 22 '18 at 17:18
@DanielB, indeed. However, why is htop now showing it in the RAM-bar as orange/yellow since it is cached? Besides, my memory usage doesn't seem to look bad (server response is fast and good). Though, when based on htop, I would conclude that my server is used at almost 100% RAM capacity? I don't understand the relation between both
– Thomas van Hesteren
Dec 22 '18 at 17:21
@DanielB, indeed. However, why is htop now showing it in the RAM-bar as orange/yellow since it is cached? Besides, my memory usage doesn't seem to look bad (server response is fast and good). Though, when based on htop, I would conclude that my server is used at almost 100% RAM capacity? I don't understand the relation between both
– Thomas van Hesteren
Dec 22 '18 at 17:21
Because it is not cached in the sense of being available for reuse. Something is still using this memory.
– Daniel B
Dec 22 '18 at 17:28
Because it is not cached in the sense of being available for reuse. Something is still using this memory.
– Daniel B
Dec 22 '18 at 17:28
|
show 1 more comment
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1386962%2fhtop-shows-massive-memory-usage-but-proceslist-shows-otherwise%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1386962%2fhtop-shows-massive-memory-usage-but-proceslist-shows-otherwise%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Are you perhaps using ZFS?
– Daniel B
Dec 22 '18 at 17:11
@DanielB no, not that I'm aware of. Where can I check this?
– Thomas van Hesteren
Dec 22 '18 at 17:13
You’d know. On second thought, the memory usage pattern doesn’t match anyway. You have a lot of shared memory, also note how your cached memory is not considered “available”.
– Daniel B
Dec 22 '18 at 17:18
@DanielB, indeed. However, why is htop now showing it in the RAM-bar as orange/yellow since it is cached? Besides, my memory usage doesn't seem to look bad (server response is fast and good). Though, when based on htop, I would conclude that my server is used at almost 100% RAM capacity? I don't understand the relation between both
– Thomas van Hesteren
Dec 22 '18 at 17:21
Because it is not cached in the sense of being available for reuse. Something is still using this memory.
– Daniel B
Dec 22 '18 at 17:28