How to analyze top command results: CPU & RAM consumption
I am working on ARM-based processor (OS version: Linux 3.4.35) and I need to analyze the processor's performance while some processes are running, by typing top command, I can see some statistics but I do not understand the details there, what information should I look for ?
Here the details I need to understand (difference between CPU usr and CPU sys, what is nic, idle, io irq and sirq and how to clear cached RAM):
Mem: 32184K used, 648K free, 0K shrd, 676K buff, 7536K cached
CPU: 11.7% usr 29.4% sys 0.0% nic 41.1% idle 11.7% io 0.0% irq 5.8% sirq
performance cpu top ram
add a comment |
I am working on ARM-based processor (OS version: Linux 3.4.35) and I need to analyze the processor's performance while some processes are running, by typing top command, I can see some statistics but I do not understand the details there, what information should I look for ?
Here the details I need to understand (difference between CPU usr and CPU sys, what is nic, idle, io irq and sirq and how to clear cached RAM):
Mem: 32184K used, 648K free, 0K shrd, 676K buff, 7536K cached
CPU: 11.7% usr 29.4% sys 0.0% nic 41.1% idle 11.7% io 0.0% irq 5.8% sirq
performance cpu top ram
add a comment |
I am working on ARM-based processor (OS version: Linux 3.4.35) and I need to analyze the processor's performance while some processes are running, by typing top command, I can see some statistics but I do not understand the details there, what information should I look for ?
Here the details I need to understand (difference between CPU usr and CPU sys, what is nic, idle, io irq and sirq and how to clear cached RAM):
Mem: 32184K used, 648K free, 0K shrd, 676K buff, 7536K cached
CPU: 11.7% usr 29.4% sys 0.0% nic 41.1% idle 11.7% io 0.0% irq 5.8% sirq
performance cpu top ram
I am working on ARM-based processor (OS version: Linux 3.4.35) and I need to analyze the processor's performance while some processes are running, by typing top command, I can see some statistics but I do not understand the details there, what information should I look for ?
Here the details I need to understand (difference between CPU usr and CPU sys, what is nic, idle, io irq and sirq and how to clear cached RAM):
Mem: 32184K used, 648K free, 0K shrd, 676K buff, 7536K cached
CPU: 11.7% usr 29.4% sys 0.0% nic 41.1% idle 11.7% io 0.0% irq 5.8% sirq
performance cpu top ram
performance cpu top ram
asked Feb 7 at 14:20
HomuncDev013HomuncDev013
82
82
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The best place to get started with learning about a given Linux/Bash command is to reference the manual page or manpage of the given command.
Here is a link to a top
manpage. In shell, you should be able to read the manpage by simply executing man top
. I will also include a link to a blog explaining top
.
The relevant part to your question can be found at section 2b. TASK and CPU States of the manpage:
As a default, percentages for these individual categories are
displayed. Where two labels are shown below, those for more recent
kernel versions are shown first.
us, user : time running un-niced user processes
sy, system : time running kernel processes
ni, nice : time running niced user processes
id, idle : time spent in the kernel idle handler
wa, IO-wait : time waiting for I/O completion
hi : time spent servicing hardware interrupts
si : time spent servicing software interrupts
us
and ni
are the percentage of CPU usage spent on un-niced and niced processes respectively. Nice values are user space processes that are either nice or not in that they can be given a priority value that either cooperates and gets out of the way of more important kernel or system processes or does not. Here is a link to a fairly straightforward explanation of niceness and priority.
The others should be rather straightforward:
idle
is how much of the processor's capacity is idle or unused. io
is the Input/Output queue of the processor. irq
and srq
are hardware and software interrupts respectively.
If you want more information on how to sort top
output, here is a relevant Stack Overflow post. Additionally if you want to know more about clearing cached memory/buffers, here is a U&L stack exchange post.
Please read over all the links I have provided and if needed you should dig a little deeper and research more into how Linux processing and memory handling works. There is a wealth of information out there online.
1
Thank you so much for this detailed and information, it helps me.
– HomuncDev013
Feb 7 at 16:01
@HomuncDev013 that is what this site is for. If you continue to need assistance, have any other questions, or feel like you have a unique and informative answer to a question on this site please reference the help center for more information.
– kemotep
Feb 7 at 16:04
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f499283%2fhow-to-analyze-top-command-results-cpu-ram-consumption%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The best place to get started with learning about a given Linux/Bash command is to reference the manual page or manpage of the given command.
Here is a link to a top
manpage. In shell, you should be able to read the manpage by simply executing man top
. I will also include a link to a blog explaining top
.
The relevant part to your question can be found at section 2b. TASK and CPU States of the manpage:
As a default, percentages for these individual categories are
displayed. Where two labels are shown below, those for more recent
kernel versions are shown first.
us, user : time running un-niced user processes
sy, system : time running kernel processes
ni, nice : time running niced user processes
id, idle : time spent in the kernel idle handler
wa, IO-wait : time waiting for I/O completion
hi : time spent servicing hardware interrupts
si : time spent servicing software interrupts
us
and ni
are the percentage of CPU usage spent on un-niced and niced processes respectively. Nice values are user space processes that are either nice or not in that they can be given a priority value that either cooperates and gets out of the way of more important kernel or system processes or does not. Here is a link to a fairly straightforward explanation of niceness and priority.
The others should be rather straightforward:
idle
is how much of the processor's capacity is idle or unused. io
is the Input/Output queue of the processor. irq
and srq
are hardware and software interrupts respectively.
If you want more information on how to sort top
output, here is a relevant Stack Overflow post. Additionally if you want to know more about clearing cached memory/buffers, here is a U&L stack exchange post.
Please read over all the links I have provided and if needed you should dig a little deeper and research more into how Linux processing and memory handling works. There is a wealth of information out there online.
1
Thank you so much for this detailed and information, it helps me.
– HomuncDev013
Feb 7 at 16:01
@HomuncDev013 that is what this site is for. If you continue to need assistance, have any other questions, or feel like you have a unique and informative answer to a question on this site please reference the help center for more information.
– kemotep
Feb 7 at 16:04
add a comment |
The best place to get started with learning about a given Linux/Bash command is to reference the manual page or manpage of the given command.
Here is a link to a top
manpage. In shell, you should be able to read the manpage by simply executing man top
. I will also include a link to a blog explaining top
.
The relevant part to your question can be found at section 2b. TASK and CPU States of the manpage:
As a default, percentages for these individual categories are
displayed. Where two labels are shown below, those for more recent
kernel versions are shown first.
us, user : time running un-niced user processes
sy, system : time running kernel processes
ni, nice : time running niced user processes
id, idle : time spent in the kernel idle handler
wa, IO-wait : time waiting for I/O completion
hi : time spent servicing hardware interrupts
si : time spent servicing software interrupts
us
and ni
are the percentage of CPU usage spent on un-niced and niced processes respectively. Nice values are user space processes that are either nice or not in that they can be given a priority value that either cooperates and gets out of the way of more important kernel or system processes or does not. Here is a link to a fairly straightforward explanation of niceness and priority.
The others should be rather straightforward:
idle
is how much of the processor's capacity is idle or unused. io
is the Input/Output queue of the processor. irq
and srq
are hardware and software interrupts respectively.
If you want more information on how to sort top
output, here is a relevant Stack Overflow post. Additionally if you want to know more about clearing cached memory/buffers, here is a U&L stack exchange post.
Please read over all the links I have provided and if needed you should dig a little deeper and research more into how Linux processing and memory handling works. There is a wealth of information out there online.
1
Thank you so much for this detailed and information, it helps me.
– HomuncDev013
Feb 7 at 16:01
@HomuncDev013 that is what this site is for. If you continue to need assistance, have any other questions, or feel like you have a unique and informative answer to a question on this site please reference the help center for more information.
– kemotep
Feb 7 at 16:04
add a comment |
The best place to get started with learning about a given Linux/Bash command is to reference the manual page or manpage of the given command.
Here is a link to a top
manpage. In shell, you should be able to read the manpage by simply executing man top
. I will also include a link to a blog explaining top
.
The relevant part to your question can be found at section 2b. TASK and CPU States of the manpage:
As a default, percentages for these individual categories are
displayed. Where two labels are shown below, those for more recent
kernel versions are shown first.
us, user : time running un-niced user processes
sy, system : time running kernel processes
ni, nice : time running niced user processes
id, idle : time spent in the kernel idle handler
wa, IO-wait : time waiting for I/O completion
hi : time spent servicing hardware interrupts
si : time spent servicing software interrupts
us
and ni
are the percentage of CPU usage spent on un-niced and niced processes respectively. Nice values are user space processes that are either nice or not in that they can be given a priority value that either cooperates and gets out of the way of more important kernel or system processes or does not. Here is a link to a fairly straightforward explanation of niceness and priority.
The others should be rather straightforward:
idle
is how much of the processor's capacity is idle or unused. io
is the Input/Output queue of the processor. irq
and srq
are hardware and software interrupts respectively.
If you want more information on how to sort top
output, here is a relevant Stack Overflow post. Additionally if you want to know more about clearing cached memory/buffers, here is a U&L stack exchange post.
Please read over all the links I have provided and if needed you should dig a little deeper and research more into how Linux processing and memory handling works. There is a wealth of information out there online.
The best place to get started with learning about a given Linux/Bash command is to reference the manual page or manpage of the given command.
Here is a link to a top
manpage. In shell, you should be able to read the manpage by simply executing man top
. I will also include a link to a blog explaining top
.
The relevant part to your question can be found at section 2b. TASK and CPU States of the manpage:
As a default, percentages for these individual categories are
displayed. Where two labels are shown below, those for more recent
kernel versions are shown first.
us, user : time running un-niced user processes
sy, system : time running kernel processes
ni, nice : time running niced user processes
id, idle : time spent in the kernel idle handler
wa, IO-wait : time waiting for I/O completion
hi : time spent servicing hardware interrupts
si : time spent servicing software interrupts
us
and ni
are the percentage of CPU usage spent on un-niced and niced processes respectively. Nice values are user space processes that are either nice or not in that they can be given a priority value that either cooperates and gets out of the way of more important kernel or system processes or does not. Here is a link to a fairly straightforward explanation of niceness and priority.
The others should be rather straightforward:
idle
is how much of the processor's capacity is idle or unused. io
is the Input/Output queue of the processor. irq
and srq
are hardware and software interrupts respectively.
If you want more information on how to sort top
output, here is a relevant Stack Overflow post. Additionally if you want to know more about clearing cached memory/buffers, here is a U&L stack exchange post.
Please read over all the links I have provided and if needed you should dig a little deeper and research more into how Linux processing and memory handling works. There is a wealth of information out there online.
edited Feb 9 at 15:21
answered Feb 7 at 15:26
kemotepkemotep
2,3143720
2,3143720
1
Thank you so much for this detailed and information, it helps me.
– HomuncDev013
Feb 7 at 16:01
@HomuncDev013 that is what this site is for. If you continue to need assistance, have any other questions, or feel like you have a unique and informative answer to a question on this site please reference the help center for more information.
– kemotep
Feb 7 at 16:04
add a comment |
1
Thank you so much for this detailed and information, it helps me.
– HomuncDev013
Feb 7 at 16:01
@HomuncDev013 that is what this site is for. If you continue to need assistance, have any other questions, or feel like you have a unique and informative answer to a question on this site please reference the help center for more information.
– kemotep
Feb 7 at 16:04
1
1
Thank you so much for this detailed and information, it helps me.
– HomuncDev013
Feb 7 at 16:01
Thank you so much for this detailed and information, it helps me.
– HomuncDev013
Feb 7 at 16:01
@HomuncDev013 that is what this site is for. If you continue to need assistance, have any other questions, or feel like you have a unique and informative answer to a question on this site please reference the help center for more information.
– kemotep
Feb 7 at 16:04
@HomuncDev013 that is what this site is for. If you continue to need assistance, have any other questions, or feel like you have a unique and informative answer to a question on this site please reference the help center for more information.
– kemotep
Feb 7 at 16:04
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f499283%2fhow-to-analyze-top-command-results-cpu-ram-consumption%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