Bug 70552
Summary: | 'top' using a LOT of cpu on highmem system | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Zarjazz <zarjazz> |
Component: | procps | Assignee: | Alexander Larsson <alexl> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-08-07 13:33:42 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Zarjazz
2002-08-02 14:02:47 UTC
Do you only see this on highmem system? This symptom was not seen previously before the current server setup however we made several changes on the system. Previously the system had 1GB of physical RAM and vanilla 2.4.18 kernel and we locked the mysqld process to use 256MB or so of this. However after the upgrade of memory to 3GB with the required 4GB highmem kernel setting and removing the memory limit on mysql the symptom appeared. We have tried the same highmem kernel on other RH server running mysql, these systems have 512MB - 1GB of RAM without the same problem with top. Not understanding how top or highmem works exactly, but to me it looks like its taking a lot of cpu to read the /proc info for each 1GB+ mysql thread. Ok. I talked to the kernel people. There is a patch that fixes this in later versions of the kernel (not the one we ship in 7.3 though, although AS has it). |