AIX 7.2 Topas show high CPUFile to access for CPU load average on AIXDiagnose high swap usage on AIXAIX cluster show swing filesystemsAIX CPU usage - how to know how many CPUs running?AIX: show video cardShow AIX operator panel statusCpu and memory utilization is high in AixAIX show package contentCalculate LPAR CPU utilization (AIX)sudo on AIX 7.2
Why no variance term in Bayesian logistic regression?
Is it inappropriate for a student to attend their mentor's dissertation defense?
Is it possible to create a QR code using text?
Avoiding the "not like other girls" trope?
A category-like structure without composition?
Why would the Red Woman birth a shadow if she worshipped the Lord of the Light?
How dangerous is XSS?
Can compressed videos be decoded back to their uncompresed original format?
Can my sorcerer use a spellbook only to collect spells and scribe scrolls, not cast?
How would I stat a creature to be immune to everything but the Magic Missile spell? (just for fun)
How seriously should I take size and weight limits of hand luggage?
How do I handle a potential work/personal life conflict as the manager of one of my friends?
Am I breaking OOP practice with this architecture?
What method can I use to design a dungeon difficult enough that the PCs can't make it through without killing them?
Reverse dictionary where values are lists
Is there an expression that means doing something right before you will need it rather than doing it in case you might need it?
Examples of smooth manifolds admitting inbetween one and a continuum of complex structures
Do UK voters know if their MP will be the Speaker of the House?
Is "remove commented out code" correct English?
Can a virus destroy the BIOS of a modern computer?
Venezuelan girlfriend wants to travel the USA to be with me. What is the process?
Is it acceptable for a professor to tell male students to not think that they are smarter than female students?
How can I deal with my CEO asking me to hire someone with a higher salary than me, a co-founder?
Why do bosons tend to occupy the same state?
AIX 7.2 Topas show high CPU
File to access for CPU load average on AIXDiagnose high swap usage on AIXAIX cluster show swing filesystemsAIX CPU usage - how to know how many CPUs running?AIX: show video cardShow AIX operator panel statusCpu and memory utilization is high in AixAIX show package contentCalculate LPAR CPU utilization (AIX)sudo on AIX 7.2
When I execute topas
for a certain process, in the CPU% column it shows me 43% and jumping to 85%.
When I execute:
"ps aux | grep processName"
The same process is at 5%.
What is more accurate? I also made a loop that similar to the Linux "watch" command, and I see it's at %5.
What's the difference between topas and ps, and who is right?
Output of ps
:
[ttfai231:root]/root>ps aux | head -1; ps aux | sort -rn +2 | head -10
USER PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 9306548 8.6 1.0 12880 12880 - A 13:35:33 41:20 MYDAEMON
root 1048868 2.0 0.0 448 448 - A 13:22:36 11:50 wait
Topas:
cpu aix ps
add a comment |
When I execute topas
for a certain process, in the CPU% column it shows me 43% and jumping to 85%.
When I execute:
"ps aux | grep processName"
The same process is at 5%.
What is more accurate? I also made a loop that similar to the Linux "watch" command, and I see it's at %5.
What's the difference between topas and ps, and who is right?
Output of ps
:
[ttfai231:root]/root>ps aux | head -1; ps aux | sort -rn +2 | head -10
USER PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 9306548 8.6 1.0 12880 12880 - A 13:35:33 41:20 MYDAEMON
root 1048868 2.0 0.0 448 448 - A 13:22:36 11:50 wait
Topas:
cpu aix ps
add a comment |
When I execute topas
for a certain process, in the CPU% column it shows me 43% and jumping to 85%.
When I execute:
"ps aux | grep processName"
The same process is at 5%.
What is more accurate? I also made a loop that similar to the Linux "watch" command, and I see it's at %5.
What's the difference between topas and ps, and who is right?
Output of ps
:
[ttfai231:root]/root>ps aux | head -1; ps aux | sort -rn +2 | head -10
USER PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 9306548 8.6 1.0 12880 12880 - A 13:35:33 41:20 MYDAEMON
root 1048868 2.0 0.0 448 448 - A 13:22:36 11:50 wait
Topas:
cpu aix ps
When I execute topas
for a certain process, in the CPU% column it shows me 43% and jumping to 85%.
When I execute:
"ps aux | grep processName"
The same process is at 5%.
What is more accurate? I also made a loop that similar to the Linux "watch" command, and I see it's at %5.
What's the difference between topas and ps, and who is right?
Output of ps
:
[ttfai231:root]/root>ps aux | head -1; ps aux | sort -rn +2 | head -10
USER PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 9306548 8.6 1.0 12880 12880 - A 13:35:33 41:20 MYDAEMON
root 1048868 2.0 0.0 448 448 - A 13:22:36 11:50 wait
Topas:
cpu aix ps
cpu aix ps
edited yesterday


Jeff Schaller♦
44.6k1162144
44.6k1162144
asked 2 days ago
ilanschilansch
1581114
1581114
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I believe this is a difference in how each field is computed. For the topas
field:
% CPU Utilization
The average processor use of the process over the monitoring interval. The first time a process is shown, this value is the average processor use over the lifetime of the process.
... while the ps
field:
%CPU
(u and v flags) The percentage of time the process has used the CPU since the process started. This value is computed by dividing the time the process uses the CPU by the elapsed time of the process. In a multi-processor environment, the value is further divided by the number of available CPUs because several threads in the same process can run on different CPUs at the same time. (Because the time base over which this data is computed varies, the sum of all %CPU fields can exceed 100%.)
I've bolded the pieces of the description that highlight the difference.
The topas
CPU% value will fluctuate as the processes uses more or less CPU time, so it will show the CPU usage over the most recent (presumably short) interval; the ps
%CPU value will always be shown as the average over the lifetime of the process.
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%2f509929%2faix-7-2-topas-show-high-cpu%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
I believe this is a difference in how each field is computed. For the topas
field:
% CPU Utilization
The average processor use of the process over the monitoring interval. The first time a process is shown, this value is the average processor use over the lifetime of the process.
... while the ps
field:
%CPU
(u and v flags) The percentage of time the process has used the CPU since the process started. This value is computed by dividing the time the process uses the CPU by the elapsed time of the process. In a multi-processor environment, the value is further divided by the number of available CPUs because several threads in the same process can run on different CPUs at the same time. (Because the time base over which this data is computed varies, the sum of all %CPU fields can exceed 100%.)
I've bolded the pieces of the description that highlight the difference.
The topas
CPU% value will fluctuate as the processes uses more or less CPU time, so it will show the CPU usage over the most recent (presumably short) interval; the ps
%CPU value will always be shown as the average over the lifetime of the process.
add a comment |
I believe this is a difference in how each field is computed. For the topas
field:
% CPU Utilization
The average processor use of the process over the monitoring interval. The first time a process is shown, this value is the average processor use over the lifetime of the process.
... while the ps
field:
%CPU
(u and v flags) The percentage of time the process has used the CPU since the process started. This value is computed by dividing the time the process uses the CPU by the elapsed time of the process. In a multi-processor environment, the value is further divided by the number of available CPUs because several threads in the same process can run on different CPUs at the same time. (Because the time base over which this data is computed varies, the sum of all %CPU fields can exceed 100%.)
I've bolded the pieces of the description that highlight the difference.
The topas
CPU% value will fluctuate as the processes uses more or less CPU time, so it will show the CPU usage over the most recent (presumably short) interval; the ps
%CPU value will always be shown as the average over the lifetime of the process.
add a comment |
I believe this is a difference in how each field is computed. For the topas
field:
% CPU Utilization
The average processor use of the process over the monitoring interval. The first time a process is shown, this value is the average processor use over the lifetime of the process.
... while the ps
field:
%CPU
(u and v flags) The percentage of time the process has used the CPU since the process started. This value is computed by dividing the time the process uses the CPU by the elapsed time of the process. In a multi-processor environment, the value is further divided by the number of available CPUs because several threads in the same process can run on different CPUs at the same time. (Because the time base over which this data is computed varies, the sum of all %CPU fields can exceed 100%.)
I've bolded the pieces of the description that highlight the difference.
The topas
CPU% value will fluctuate as the processes uses more or less CPU time, so it will show the CPU usage over the most recent (presumably short) interval; the ps
%CPU value will always be shown as the average over the lifetime of the process.
I believe this is a difference in how each field is computed. For the topas
field:
% CPU Utilization
The average processor use of the process over the monitoring interval. The first time a process is shown, this value is the average processor use over the lifetime of the process.
... while the ps
field:
%CPU
(u and v flags) The percentage of time the process has used the CPU since the process started. This value is computed by dividing the time the process uses the CPU by the elapsed time of the process. In a multi-processor environment, the value is further divided by the number of available CPUs because several threads in the same process can run on different CPUs at the same time. (Because the time base over which this data is computed varies, the sum of all %CPU fields can exceed 100%.)
I've bolded the pieces of the description that highlight the difference.
The topas
CPU% value will fluctuate as the processes uses more or less CPU time, so it will show the CPU usage over the most recent (presumably short) interval; the ps
%CPU value will always be shown as the average over the lifetime of the process.
answered yesterday


Jeff Schaller♦Jeff Schaller
44.6k1162144
44.6k1162144
add a comment |
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%2f509929%2faix-7-2-topas-show-high-cpu%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