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 1320334 - Regression in Xorg CPU usage between 6.4 and 6.7
Summary: Regression in Xorg CPU usage between 6.4 and 6.7
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-server
Version: 6.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Adam Jackson
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-22 21:24 UTC by Dave Johansen
Modified: 2020-08-13 08:25 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-01 21:29:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Run 35 xeyes instances to show the increased CPU usage of Xorg (200 bytes, application/x-shellscript)
2016-03-22 21:24 UTC, Dave Johansen 		no flags Details
View All

Description Dave Johansen 2016-03-22 21:24:46 UTC 
Created attachment 1139236 [details]
Run 35 xeyes instances to show the increased CPU usage of Xorg

Description of problem:
Xorg is taking significantly more CPU with 6.7 than it did with 6.4.

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.15.0-36

How reproducible:
Always

Steps to Reproduce:
1. Run attached test_xorg script
2. Move mouse back and forth so that xeyes keeps moving and redrawing

Actual results:
CPU usage is 2-3x what is was with RHEL 6.4.

Expected results:
CPU usage should be the same for all RHEL 6.x releases.

Additional info:
This issue is affecting our applications and this is just a simple reproducer that I could come up with to demonstrate the issue.
Comment 2 tlrader 2016-06-01 17:51:40 UTC 
We encountered this same issue on our new RHEL7.2 workstations; however, when we upgraded to the newer kernel 4; the problem went away.
Comment 4 linferna 2017-01-13 06:14:57 UTC 
I have been experiencing same behavior with high cpu load on Xorg process resulting sluggish performance. I am using RHEL 6.7 kernel with xorg-x11-server-Xorg-1.15.0-36.el6.x86_64. I have noticed xorg/high cpu load issues with RHEL 6.7 firefox (45.1.0). I noticed various splash screens trigger this behavior. Once the offending FF tab or FF session is closed, then the Xorg settles down to acceptable low CPU load and regain the performance on the workstation.
Comment 5 Chris Williams 2017-06-01 21:29:21 UTC 
Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017.  During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not appear to meet the inclusion criteria for the Production Phase 3 and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification.  Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com
Note You need to log in before you can comment on or make changes to this bug.