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 1919964 - [RFE] Reduce stalld CPU usage: do not parse almost idle CPUs
Summary: [RFE] Reduce stalld CPU usage: do not parse almost idle CPUs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: stalld
Version: 8.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: Clark Williams
QA Contact: Mark Simmons
URL:
Whiteboard:
Depends On:
Blocks: 1898189
TreeView+ depends on / blocked
 
Reported: 2021-01-25 13:32 UTC by Daniel Bristot de Oliveira
Modified: 2021-05-18 16:06 UTC (History)
7 users (show)

Fixed In Version: stalld-1.9-2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-18 16:06:47 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2021:1918 0 None None None 2021-05-18 16:06:54 UTC

Description Daniel Bristot de Oliveira 2021-01-25 13:32:23 UTC
Description of problem:

On large systems, stalld is consuming a noticeable amount of CPU time, even when the system is idle.

This happens because stalld parses the /proc/sched_debug for all CPUs, even when the system is almost idle. This can be improved by skipping the CPUs' parse that had some idle time since the last check.

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

How reproducible:
Always

Steps to Reproduce:
1. Start the system and watch it on top tool

Actual results:
Considerable CPU usage


Expected results:
Low CPU usage when the system is not at risk of facing starvation.

Additional info:

Comment 2 Daniel Bristot de Oliveira 2021-02-25 10:47:13 UTC
The 1.9 version of stalld implements idle detection by parsing the (small) /proc/stat.

It works by skipping:
	- Reading the huge /proc/sched_debug if all CPUs had idle time.
	- Reading the huge /proc/sched_debug if a CPU with its own stalld thread had idle time.
	- Parsing the sched_debug buffer for CPUs with idle time.

This feature reduces the stalld cpu usage to the point that it becomes almost invisible on the top tool when the system is idle.

More information can be found in this commit.
https://gitlab.com/rt-linux-tools/stalld/-/commit/b2866594aaea3369abfbed8da3af16d66cdb4d99

Clark has more info about the inclusion of this version on RHEL.

Comment 10 errata-xmlrpc 2021-05-18 16:06:47 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (stalld bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2021:1918


Note You need to log in before you can comment on or make changes to this bug.