This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2155424 - ListUnitFiles impacts systemd a lot, causing high CPU consumption and delay in operations
Summary: ListUnitFiles impacts systemd a lot, causing high CPU consumption and delay i...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: systemd
Version: 9.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: systemd maint
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-21 08:38 UTC by Renaud Métrich
Modified: 2023-09-21 12:20 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-21 12:20:03 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-5961 0 None Migrated None 2023-09-21 12:19:59 UTC
Red Hat Issue Tracker RHELPLAN-143007 0 None None None 2022-12-21 08:40:23 UTC

Description Renaud Métrich 2022-12-21 08:38:26 UTC 
Description of problem:

This is a respin of BZ #1828759 ("systemctl list-unit-files" kills the system usability).

With RHEL8.7 / systemd-239-68.el8 (didn't check with older ones yet), we can see that the ListUnitFiles DBus operation is very costly.
When executing systemd under strace, we can observe that on a system having 145 units ("minimal installation" of RHEL8.7), the readlinkat/openat/getdents64 syscalls are called hundreds or even thousands of times on same files (see reproducer below), causing high CPU consumption.


Version-Release number of selected component (if applicable):

systemd-239-68.el8

How reproducible:

Always

Steps to Reproduce:
1. Execute the DBus ListUnitFiles operation while stracing systemd

    # strace -CttTvyy -s 128 -o list-unit-files.strace -p 1 &
    # time dbus-send --system --print-reply --reply-timeout=20000 --type=method_call --dest=org.freedesktop.systemd1 /org/freedesktop/systemd1 org.freedesktop.systemd1.Manager.ListUnitFiles
    # kill %1

2. Check number of syscalls

    # tail -20 list-unit-files.strace
    % time     seconds  usecs/call     calls    errors syscall
    ------ ----------- ----------- --------- --------- ----------------
     30.08    0.277966           2    119048           readlinkat
     21.62    0.199787           2     79554     16869 openat
     21.01    0.194170           2     89605           getdents64
     10.02    0.092602           1     90426           fcntl
    ...

3. Check number of times readlinkat() is executed on a given path

    # grep " readlinkat(" list-unit-files.strace | cut -f2 -d'"' | sort | uniq -c | sort -k1 -rn > list-unit-files.strace.readlinkat
    # head list-unit-files.strace.readlinkat
    820 /etc/systemd/system/syslog.service
    819 /etc/systemd/system/multi-user.target.wants/remote-fs.target
    818 /etc/systemd/system/multi-user.target.wants/crond.service
    817 /etc/systemd/system/multi-user.target.wants/NetworkManager.service
    815 /etc/systemd/system/multi-user.target.wants/dnf-makecache.timer
    814 /etc/systemd/system/multi-user.target.wants/sssd.service
    ...

    # grep "NetworkManager.service" list-unit-files.strace.readlinkat
    817 /etc/systemd/system/multi-user.target.wants/NetworkManager.service
    793 /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service

Actual results:

Slowness, CPU consumption

Expected results:

Files/Symlinks resolved once.
Comment 23 RHEL Program Management 2023-09-21 12:16:22 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 24 RHEL Program Management 2023-09-21 12:20:03 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.