Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 583761[details]
result show on "mpstat 1 59 "
Description of problem:
when doing performance testing of kvm network, we usually use mpstat to measure the cpu usage on host.sometimes exceptional average report is showed like "Average: all 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00"
Version-Release number of selected component (if applicable):
sysstat-9.0.4-20.el6.x86_64
How reproducible:
sometimes
Steps to Reproduce:
1.boot up a guest
2.do netperf tests on guest,at the same time. measure cpu usage on host by using "mpstat 1 59"
3.check the attached the result
Actual results:
Expected results:
cpu average can be computed well.
Additional info:
(In reply to comment #3)
> Quan,
>
> please, was this issue also fixed in kernel-2.6.32-275.el6 (as the result of
> bug #820507)?
>
> Thanks,
>
> peter
Yes, did not hit this issue in kernel-2.6.32-277.el6.
But I am interesting in how does average of mpstat computed, bug #820507 will only affect result of certain seconds, why all "zero" show in the average report.
Hi Quan,
the average is counted the same way as the rest of the statistics - difference between the two values; for average it is the first and last value. Also, there is the check whether the first value is not bigger than the second, what could happen with bug #820507.. so I think the zero average is from there..
Can I close this bug as a duplicate?
Thanks,
peter
(In reply to comment #5)
> Hi Quan,
>
> the average is counted the same way as the rest of the statistics -
> difference between the two values; for average it is the first and last
> value. Also, there is the check whether the first value is not bigger than
> the second, what could happen with bug #820507.. so I think the zero average
> is from there..
Thanks for your comment.
> Can I close this bug as a duplicate?
Yes,pease.
> Thanks,
>
> peter
Created attachment 583761 [details] result show on "mpstat 1 59 " Description of problem: when doing performance testing of kvm network, we usually use mpstat to measure the cpu usage on host.sometimes exceptional average report is showed like "Average: all 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00" Version-Release number of selected component (if applicable): sysstat-9.0.4-20.el6.x86_64 How reproducible: sometimes Steps to Reproduce: 1.boot up a guest 2.do netperf tests on guest,at the same time. measure cpu usage on host by using "mpstat 1 59" 3.check the attached the result Actual results: Expected results: cpu average can be computed well. Additional info: