top command occupied high cpu usage Announcing the arrival of Valued Associate #679: Cesar...
What does an IRS interview request entail when called in to verify expenses for a sole proprietor small business?
3 doors, three guards, one stone
How to react to hostile behavior from a senior developer?
How to deal with a team lead who never gives me credit?
Can an alien society believe that their star system is the universe?
How to bypass password on Windows XP account?
How to run gsettings for another user Ubuntu 18.04.2 LTS
prime numbers and expressing non-prime numbers
Generate an RGB colour grid
How can I make names more distinctive without making them longer?
Storing hydrofluoric acid before the invention of plastics
Do I really need recursive chmod to restrict access to a folder?
How to align text above triangle figure
Why are there no cargo aircraft with "flying wing" design?
Denied boarding although I have proper visa and documentation. To whom should I make a complaint?
How to tell that you are a giant?
Is it true that "carbohydrates are of no use for the basal metabolic need"?
Short Story with Cinderella as a Voo-doo Witch
Bete Noir -- no dairy
Fundamental Solution of the Pell Equation
Why is "Consequences inflicted." not a sentence?
How does debian/ubuntu knows a package has a updated version
Using audio cues to encourage good posture
Why are Kinder Surprise Eggs illegal in the USA?
top command occupied high cpu usage
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!Confused by CPU values in Unix 'top' commandtop: What does cpu usage mean?High CPU load but top processes in top all around 0%top command indicates a different cpu usage than sar commandLinux top command. Memory usageTop not showing processes using CPU resourcesDiagnosing high CPU waitingHigh CPU usage without useful information from top commandCpu usage percentage with TopTop command - overall cpu usage is lesser than process' cpu usage
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
My system is SUSE 10 and I observe that top occupies 57% CPU usage when I use it.
I don't have too many processes:
ps -eLf | wc -l
106
Here are top's stats:
cat /proc/2913/stat
2913 (top) R 2879 2913 2879 34819 2913 8396800 411 0 0 0 60648 199580 0 0 17 0 1 516504552 4811013274 2383872 285 4294967295 134512640 134596384 3215474448 3215470376 3085449998 0 0 0 138047495 0 0 0 17 3 0 0 0
cat /proc/2913/status
Name: top
State: R (running)
SleepAVG: 79%
Tgid: 2913
Pid: 2913
PPid: 2879
TracerPid: 0
Uid: 0 0 0 0
Gid: 0 0 0 0
FDSize: 256
Groups: 0
VmPeak: 2360 kB
VmSize: 2328 kB
VmLck: 0 kB
VmHWM: 1144 kB
VmRSS: 1140 kB
VmData: 260 kB
VmStk: 84 kB
VmExe: 84 kB
VmLib: 1788 kB
VmPTE: 16 kB
Threads: 1
SigQ: 2/16383
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000000000000
SigCgt: 00000000083a7007
CapInh: 0000000000000000
CapPrm: 00000000fffffeff
CapEff: 00000000fffffeff
Cpus_allowed: 00000000,00000000,00000000,0000000f
Mems_allowed: 1
## cat /proc/2913/statm
582 285 213 21 0 86 0
What can I do next to find the reason why the top command is using so much CPU?
linux central-processing-unit top
edited Mar 12 '12 at 5:29
Wesley
29.3k867113
asked Mar 12 '12 at 4:43
DaVidDaVid
1623
bumped to the homepage by Community♦ 4 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
My system is SUSE 10 and I observe that top occupies 57% CPU usage when I use it.
I don't have too many processes:
ps -eLf | wc -l
106
Here are top's stats:
cat /proc/2913/stat
2913 (top) R 2879 2913 2879 34819 2913 8396800 411 0 0 0 60648 199580 0 0 17 0 1 516504552 4811013274 2383872 285 4294967295 134512640 134596384 3215474448 3215470376 3085449998 0 0 0 138047495 0 0 0 17 3 0 0 0
cat /proc/2913/status
Name: top
State: R (running)
SleepAVG: 79%
Tgid: 2913
Pid: 2913
PPid: 2879
TracerPid: 0
Uid: 0 0 0 0
Gid: 0 0 0 0
FDSize: 256
Groups: 0
VmPeak: 2360 kB
VmSize: 2328 kB
VmLck: 0 kB
VmHWM: 1144 kB
VmRSS: 1140 kB
VmData: 260 kB
VmStk: 84 kB
VmExe: 84 kB
VmLib: 1788 kB
VmPTE: 16 kB
Threads: 1
SigQ: 2/16383
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000000000000
SigCgt: 00000000083a7007
CapInh: 0000000000000000
CapPrm: 00000000fffffeff
CapEff: 00000000fffffeff
Cpus_allowed: 00000000,00000000,00000000,0000000f
Mems_allowed: 1
## cat /proc/2913/statm
582 285 213 21 0 86 0
What can I do next to find the reason why the top command is using so much CPU?
linux central-processing-unit top
edited Mar 12 '12 at 5:29
Wesley
29.3k867113
asked Mar 12 '12 at 4:43
DaVidDaVid
1623
bumped to the homepage by Community♦ 4 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I find the root cause。
– DaVid
Mar 13 '12 at 2:40
top will read /var/run/utmp file to get active user number. But this file is so big with 178M. top spends about 8s to read it that maybe occupies 57% CPU usage. Change utmp size to 10 K, top command doesn't occupy more CPU usage.
– DaVid
Mar 13 '12 at 2:42
You should post this as an answer and accept it, otherwise the question will pop up again and again because it is not marked as "solved".
– Gerald Schneider
Sep 12 '18 at 10:09
1
On a side note, an uptime of 556 days also means that you aren't running the newest kernel, and most probably also not the current version of the services you are running on the machine. This is a security risk.
– Gerald Schneider
Sep 12 '18 at 10:10
add a comment |
My system is SUSE 10 and I observe that top occupies 57% CPU usage when I use it.
I don't have too many processes:
ps -eLf | wc -l
106
Here are top's stats:
cat /proc/2913/stat
2913 (top) R 2879 2913 2879 34819 2913 8396800 411 0 0 0 60648 199580 0 0 17 0 1 516504552 4811013274 2383872 285 4294967295 134512640 134596384 3215474448 3215470376 3085449998 0 0 0 138047495 0 0 0 17 3 0 0 0
cat /proc/2913/status
Name: top
State: R (running)
SleepAVG: 79%
Tgid: 2913
Pid: 2913
PPid: 2879
TracerPid: 0
Uid: 0 0 0 0
Gid: 0 0 0 0
FDSize: 256
Groups: 0
VmPeak: 2360 kB
VmSize: 2328 kB
VmLck: 0 kB
VmHWM: 1144 kB
VmRSS: 1140 kB
VmData: 260 kB
VmStk: 84 kB
VmExe: 84 kB
VmLib: 1788 kB
VmPTE: 16 kB
Threads: 1
SigQ: 2/16383
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000000000000
SigCgt: 00000000083a7007
CapInh: 0000000000000000
CapPrm: 00000000fffffeff
CapEff: 00000000fffffeff
Cpus_allowed: 00000000,00000000,00000000,0000000f
Mems_allowed: 1
## cat /proc/2913/statm
582 285 213 21 0 86 0
What can I do next to find the reason why the top command is using so much CPU?
linux central-processing-unit top
edited Mar 12 '12 at 5:29
Wesley
29.3k867113
asked Mar 12 '12 at 4:43
DaVidDaVid
1623
My system is SUSE 10 and I observe that top occupies 57% CPU usage when I use it.
I don't have too many processes:
ps -eLf | wc -l
106
Here are top's stats:
cat /proc/2913/stat
2913 (top) R 2879 2913 2879 34819 2913 8396800 411 0 0 0 60648 199580 0 0 17 0 1 516504552 4811013274 2383872 285 4294967295 134512640 134596384 3215474448 3215470376 3085449998 0 0 0 138047495 0 0 0 17 3 0 0 0
cat /proc/2913/status
Name: top
State: R (running)
SleepAVG: 79%
Tgid: 2913
Pid: 2913
PPid: 2879
TracerPid: 0
Uid: 0 0 0 0
Gid: 0 0 0 0
FDSize: 256
Groups: 0
VmPeak: 2360 kB
VmSize: 2328 kB
VmLck: 0 kB
VmHWM: 1144 kB
VmRSS: 1140 kB
VmData: 260 kB
VmStk: 84 kB
VmExe: 84 kB
VmLib: 1788 kB
VmPTE: 16 kB
Threads: 1
SigQ: 2/16383
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000000000000
SigCgt: 00000000083a7007
CapInh: 0000000000000000
CapPrm: 00000000fffffeff
CapEff: 00000000fffffeff
Cpus_allowed: 00000000,00000000,00000000,0000000f
Mems_allowed: 1
## cat /proc/2913/statm
582 285 213 21 0 86 0
What can I do next to find the reason why the top command is using so much CPU?
linux central-processing-unit top
linux central-processing-unit top
edited Mar 12 '12 at 5:29
Wesley
29.3k867113
asked Mar 12 '12 at 4:43
DaVidDaVid
1623
edited Mar 12 '12 at 5:29
Wesley
29.3k867113
asked Mar 12 '12 at 4:43
DaVidDaVid
1623
edited Mar 12 '12 at 5:29
Wesley
29.3k867113
edited Mar 12 '12 at 5:29
Wesley
29.3k867113
edited Mar 12 '12 at 5:29
Wesley
29.3k867113
29.3k867113
asked Mar 12 '12 at 4:43
DaVidDaVid
1623
asked Mar 12 '12 at 4:43
DaVidDaVid
1623
asked Mar 12 '12 at 4:43
DaVidDaVid
1623
1623
bumped to the homepage by Community♦ 4 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 4 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I find the root cause。
– DaVid
Mar 13 '12 at 2:40
top will read /var/run/utmp file to get active user number. But this file is so big with 178M. top spends about 8s to read it that maybe occupies 57% CPU usage. Change utmp size to 10 K, top command doesn't occupy more CPU usage.
– DaVid
Mar 13 '12 at 2:42
You should post this as an answer and accept it, otherwise the question will pop up again and again because it is not marked as "solved".
– Gerald Schneider
Sep 12 '18 at 10:09
1
On a side note, an uptime of 556 days also means that you aren't running the newest kernel, and most probably also not the current version of the services you are running on the machine. This is a security risk.
– Gerald Schneider
Sep 12 '18 at 10:10
add a comment |
I find the root cause。
– DaVid
Mar 13 '12 at 2:40
top will read /var/run/utmp file to get active user number. But this file is so big with 178M. top spends about 8s to read it that maybe occupies 57% CPU usage. Change utmp size to 10 K, top command doesn't occupy more CPU usage.
– DaVid
Mar 13 '12 at 2:42
You should post this as an answer and accept it, otherwise the question will pop up again and again because it is not marked as "solved".
– Gerald Schneider
Sep 12 '18 at 10:09
1
On a side note, an uptime of 556 days also means that you aren't running the newest kernel, and most probably also not the current version of the services you are running on the machine. This is a security risk.
– Gerald Schneider
Sep 12 '18 at 10:10
I find the root cause。
– DaVid
Mar 13 '12 at 2:40
I find the root cause。
– DaVid
Mar 13 '12 at 2:40
top will read /var/run/utmp file to get active user number. But this file is so big with 178M. top spends about 8s to read it that maybe occupies 57% CPU usage. Change utmp size to 10 K, top command doesn't occupy more CPU usage.
– DaVid
Mar 13 '12 at 2:42
top will read /var/run/utmp file to get active user number. But this file is so big with 178M. top spends about 8s to read it that maybe occupies 57% CPU usage. Change utmp size to 10 K, top command doesn't occupy more CPU usage.
– DaVid
Mar 13 '12 at 2:42
You should post this as an answer and accept it, otherwise the question will pop up again and again because it is not marked as "solved".
– Gerald Schneider
Sep 12 '18 at 10:09
You should post this as an answer and accept it, otherwise the question will pop up again and again because it is not marked as "solved".
– Gerald Schneider
Sep 12 '18 at 10:09
1
1
On a side note, an uptime of 556 days also means that you aren't running the newest kernel, and most probably also not the current version of the services you are running on the machine. This is a security risk.
– Gerald Schneider
Sep 12 '18 at 10:10
On a side note, an uptime of 556 days also means that you aren't running the newest kernel, and most probably also not the current version of the services you are running on the machine. This is a security risk.
– Gerald Schneider
Sep 12 '18 at 10:10
add a comment |
2 Answers
2
active
oldest
votes
Your server is up 556 days. Though this shouldn't be a problem it is possible the long uptime is causing some funky behaviour like you're noticing. Without any identifiable cause. In my experience in such situations a fresh reboot clears up the problem right away. I understand it's a stupid solution, but why waste more time figuring it out?
If a reboot doesn't fix it then it's worth looking into it more deeply.
answered Mar 12 '12 at 21:06
aseqaseq
3,94011639
As you know, reboot is not a good way. Top command is a more popular tool to investigate other problem for Maintenance Engineer or Operation Engineer.
– DaVid
Mar 13 '12 at 2:47
Yes but it's his top command that is behaving strangely, i.e. it's using more CPU % than it should. Top normally only uses a couple of %. In this case using top to find out why top is behaving strangely is not the best thing to do. :-)
– aseq
Mar 13 '12 at 18:28
add a comment |
top is only using 1/8th of the CPU power of your ?netbook?
you can see from this line:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2913 root 16 0 2328 1140 852 R 57 0.1 38:15.95 top
that it is only using what it says is 57%, while there are 94 tasks that are sleeping:
Tasks: 95 total, 1 running, 94 sleeping, O stopped, O zombie
you can then direct your attention to the middle section:
Cpu0 : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpul : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu2 : 0.0%us, 0.0%sy, 0.0%ni, 99.7%id, 0.3%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu3 :13.3%us,43.6%sy, 0.0%ni, 43.0%id, 0.1%wa, 0.0%hi, 0.0%si, 0.0%st
CPU0 is 100% in the idle state, as is CPU1 and CPU2, CPU3 is only occupying 43% of the time with system processes, and 13% of the time with user processes.
as the man 1 top page says:
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
st : time stolen from this vm by the hypervisor
top is only using
57/4% or 14%
of your processing power and only
.1%
of your memory.
answered Nov 14 '18 at 15:25
ChrisChris
112
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
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%2fserverfault.com%2fquestions%2f368683%2ftop-command-occupied-high-cpu-usage%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Your server is up 556 days. Though this shouldn't be a problem it is possible the long uptime is causing some funky behaviour like you're noticing. Without any identifiable cause. In my experience in such situations a fresh reboot clears up the problem right away. I understand it's a stupid solution, but why waste more time figuring it out?
If a reboot doesn't fix it then it's worth looking into it more deeply.
answered Mar 12 '12 at 21:06
aseqaseq
3,94011639
As you know, reboot is not a good way. Top command is a more popular tool to investigate other problem for Maintenance Engineer or Operation Engineer.
– DaVid
Mar 13 '12 at 2:47
Yes but it's his top command that is behaving strangely, i.e. it's using more CPU % than it should. Top normally only uses a couple of %. In this case using top to find out why top is behaving strangely is not the best thing to do. :-)
– aseq
Mar 13 '12 at 18:28
add a comment |
Your server is up 556 days. Though this shouldn't be a problem it is possible the long uptime is causing some funky behaviour like you're noticing. Without any identifiable cause. In my experience in such situations a fresh reboot clears up the problem right away. I understand it's a stupid solution, but why waste more time figuring it out?
If a reboot doesn't fix it then it's worth looking into it more deeply.
answered Mar 12 '12 at 21:06
aseqaseq
3,94011639
As you know, reboot is not a good way. Top command is a more popular tool to investigate other problem for Maintenance Engineer or Operation Engineer.
– DaVid
Mar 13 '12 at 2:47
Yes but it's his top command that is behaving strangely, i.e. it's using more CPU % than it should. Top normally only uses a couple of %. In this case using top to find out why top is behaving strangely is not the best thing to do. :-)
– aseq
Mar 13 '12 at 18:28
add a comment |
Your server is up 556 days. Though this shouldn't be a problem it is possible the long uptime is causing some funky behaviour like you're noticing. Without any identifiable cause. In my experience in such situations a fresh reboot clears up the problem right away. I understand it's a stupid solution, but why waste more time figuring it out?
If a reboot doesn't fix it then it's worth looking into it more deeply.
answered Mar 12 '12 at 21:06
aseqaseq
3,94011639
Your server is up 556 days. Though this shouldn't be a problem it is possible the long uptime is causing some funky behaviour like you're noticing. Without any identifiable cause. In my experience in such situations a fresh reboot clears up the problem right away. I understand it's a stupid solution, but why waste more time figuring it out?
If a reboot doesn't fix it then it's worth looking into it more deeply.
answered Mar 12 '12 at 21:06
aseqaseq
3,94011639
answered Mar 12 '12 at 21:06
aseqaseq
3,94011639
answered Mar 12 '12 at 21:06
aseqaseq
3,94011639
answered Mar 12 '12 at 21:06
aseqaseq
3,94011639
3,94011639
As you know, reboot is not a good way. Top command is a more popular tool to investigate other problem for Maintenance Engineer or Operation Engineer.
– DaVid
Mar 13 '12 at 2:47
Yes but it's his top command that is behaving strangely, i.e. it's using more CPU % than it should. Top normally only uses a couple of %. In this case using top to find out why top is behaving strangely is not the best thing to do. :-)
– aseq
Mar 13 '12 at 18:28
add a comment |
As you know, reboot is not a good way. Top command is a more popular tool to investigate other problem for Maintenance Engineer or Operation Engineer.
– DaVid
Mar 13 '12 at 2:47
Yes but it's his top command that is behaving strangely, i.e. it's using more CPU % than it should. Top normally only uses a couple of %. In this case using top to find out why top is behaving strangely is not the best thing to do. :-)
– aseq
Mar 13 '12 at 18:28
As you know, reboot is not a good way. Top command is a more popular tool to investigate other problem for Maintenance Engineer or Operation Engineer.
– DaVid
Mar 13 '12 at 2:47
As you know, reboot is not a good way. Top command is a more popular tool to investigate other problem for Maintenance Engineer or Operation Engineer.
– DaVid
Mar 13 '12 at 2:47
Yes but it's his top command that is behaving strangely, i.e. it's using more CPU % than it should. Top normally only uses a couple of %. In this case using top to find out why top is behaving strangely is not the best thing to do. :-)
– aseq
Mar 13 '12 at 18:28
Yes but it's his top command that is behaving strangely, i.e. it's using more CPU % than it should. Top normally only uses a couple of %. In this case using top to find out why top is behaving strangely is not the best thing to do. :-)
– aseq
Mar 13 '12 at 18:28
add a comment |
top is only using 1/8th of the CPU power of your ?netbook?
you can see from this line:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2913 root 16 0 2328 1140 852 R 57 0.1 38:15.95 top
that it is only using what it says is 57%, while there are 94 tasks that are sleeping:
Tasks: 95 total, 1 running, 94 sleeping, O stopped, O zombie
you can then direct your attention to the middle section:
Cpu0 : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpul : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu2 : 0.0%us, 0.0%sy, 0.0%ni, 99.7%id, 0.3%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu3 :13.3%us,43.6%sy, 0.0%ni, 43.0%id, 0.1%wa, 0.0%hi, 0.0%si, 0.0%st
CPU0 is 100% in the idle state, as is CPU1 and CPU2, CPU3 is only occupying 43% of the time with system processes, and 13% of the time with user processes.
as the man 1 top page says:
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
st : time stolen from this vm by the hypervisor
top is only using
57/4% or 14%
of your processing power and only
.1%
of your memory.
answered Nov 14 '18 at 15:25
ChrisChris
112
add a comment |
top is only using 1/8th of the CPU power of your ?netbook?
you can see from this line:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2913 root 16 0 2328 1140 852 R 57 0.1 38:15.95 top
that it is only using what it says is 57%, while there are 94 tasks that are sleeping:
Tasks: 95 total, 1 running, 94 sleeping, O stopped, O zombie
you can then direct your attention to the middle section:
Cpu0 : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpul : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu2 : 0.0%us, 0.0%sy, 0.0%ni, 99.7%id, 0.3%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu3 :13.3%us,43.6%sy, 0.0%ni, 43.0%id, 0.1%wa, 0.0%hi, 0.0%si, 0.0%st
CPU0 is 100% in the idle state, as is CPU1 and CPU2, CPU3 is only occupying 43% of the time with system processes, and 13% of the time with user processes.
as the man 1 top page says:
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
st : time stolen from this vm by the hypervisor
top is only using
57/4% or 14%
of your processing power and only
.1%
of your memory.
answered Nov 14 '18 at 15:25
ChrisChris
112
add a comment |
top is only using 1/8th of the CPU power of your ?netbook?
you can see from this line:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2913 root 16 0 2328 1140 852 R 57 0.1 38:15.95 top
that it is only using what it says is 57%, while there are 94 tasks that are sleeping:
Tasks: 95 total, 1 running, 94 sleeping, O stopped, O zombie
you can then direct your attention to the middle section:
Cpu0 : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpul : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu2 : 0.0%us, 0.0%sy, 0.0%ni, 99.7%id, 0.3%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu3 :13.3%us,43.6%sy, 0.0%ni, 43.0%id, 0.1%wa, 0.0%hi, 0.0%si, 0.0%st
CPU0 is 100% in the idle state, as is CPU1 and CPU2, CPU3 is only occupying 43% of the time with system processes, and 13% of the time with user processes.
as the man 1 top page says:
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
st : time stolen from this vm by the hypervisor
top is only using
57/4% or 14%
of your processing power and only
.1%
of your memory.
answered Nov 14 '18 at 15:25
ChrisChris
112
top is only using 1/8th of the CPU power of your ?netbook?
you can see from this line:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2913 root 16 0 2328 1140 852 R 57 0.1 38:15.95 top
that it is only using what it says is 57%, while there are 94 tasks that are sleeping:
Tasks: 95 total, 1 running, 94 sleeping, O stopped, O zombie
you can then direct your attention to the middle section:
Cpu0 : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpul : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu2 : 0.0%us, 0.0%sy, 0.0%ni, 99.7%id, 0.3%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu3 :13.3%us,43.6%sy, 0.0%ni, 43.0%id, 0.1%wa, 0.0%hi, 0.0%si, 0.0%st
CPU0 is 100% in the idle state, as is CPU1 and CPU2, CPU3 is only occupying 43% of the time with system processes, and 13% of the time with user processes.
as the man 1 top page says:
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
st : time stolen from this vm by the hypervisor
top is only using
57/4% or 14%
of your processing power and only
.1%
of your memory.
answered Nov 14 '18 at 15:25
ChrisChris
112
answered Nov 14 '18 at 15:25
ChrisChris
112
answered Nov 14 '18 at 15:25
ChrisChris
112
answered Nov 14 '18 at 15:25
ChrisChris
112
112
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f368683%2ftop-command-occupied-high-cpu-usage%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
I find the root cause。
– DaVid
Mar 13 '12 at 2:40
top will read /var/run/utmp file to get active user number. But this file is so big with 178M. top spends about 8s to read it that maybe occupies 57% CPU usage. Change utmp size to 10 K, top command doesn't occupy more CPU usage.
– DaVid
Mar 13 '12 at 2:42
You should post this as an answer and accept it, otherwise the question will pop up again and again because it is not marked as "solved".
– Gerald Schneider
Sep 12 '18 at 10:09
1
On a side note, an uptime of 556 days also means that you aren't running the newest kernel, and most probably also not the current version of the services you are running on the machine. This is a security risk.
– Gerald Schneider
Sep 12 '18 at 10:10