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.

Description of problem:

Hello,

on the following aarch64 system https://beaker.engineering.redhat.com/view/armatura2.slevarna.tpb.lab.eng.brq.redhat.com#details

CPU(s):                 224
2x Cavium ThunderX2(R) CPU CN9975 v2.2 @ 2.0GHz
https://en.wikichip.org/wiki/cavium/thunderx2/cn9975

we observe the poor performance of the trace-cmd record command on RHEL-8. It's slower by factor 2.5x compared to RHEL-9:

RHEL-8.6.0-20211121.1 4.18.0-350.el8.aarch64 
$ time trace-cmd record --quiet -e sched:sched_move_numa sleep 0.1
real    0m26.354s
user    0m0.178s
sys     0m0.188s


RHEL-9.0.0-20211213.3 5.14.0-29.el9.aarch64
$ time trace-cmd record --quiet -e sched:sched_move_numa sleep 0.1
real    0m10.697s
user    0m0.418s
sys     0m0.324s


On x86_64, trace-cmd record performance on RHEL-8 is OK:
RHEL-8.6.0-20211121.1 4.18.0-350.el8.x86_64
128 CPUs
https://beaker.engineering.redhat.com/view/amd-epyc2-rome-7502-2s.lab.eng.brq.redhat.com#details
$ time trace-cmd record --quiet -e sched:sched_move_numa sleep 0.1
real    0m4.062s
user    0m0.028s
sys     0m0.214s


It seems that only aarch64 is affected. 

Could you please investigate the problem and check if we can reach the same performance of trace-cmd record as on RHEL-9? 

Thanks a lot!
Jirka

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.