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 639795 - Performance Tuning Guide: TRACKING BUG for [MEMORY] [VM Tuning]
Summary: Performance Tuning Guide: TRACKING BUG for [MEMORY] [VM Tuning]
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Deadline: 2011-07-22
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Performance_Tuning_Guide
Version: 6.2
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Laura Bailey
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks: 639779
TreeView+ depends on / blocked
 
Reported: 2010-10-04 02:38 UTC by Don Domingo
Modified: 2011-10-31 01:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-31 01:07:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 7 Larry Woodman 2011-08-23 12:05:40 UTC

1.) NEEDINFO: pagecache

RHEL6 does no have the /proc/sys/vm/pagecache tunable parameter.

2.) NEEDINFO: slabcache

Not sure what this means, there is no slabcache file in the /proc filesystem.

3.) min_free_kbytes

Be cautious when setting this parameter, as both too-low and too-high values can be damaging.
Setting it to a value lower than 1024 KB results in a system that is prone to deadlock under high loads. A reason for this would be nice.
However, setting this parameter to a value that is too high will cause your system to become out-of-memory immediately. I assume "too high" is "as much/more memory than your system has available". 

Setting min_free_kbytes too low will prevent the system from reclaiming memory all together.  This can result in system hangs and/or OOM killing several processes.

Too high is something like 5% - 10% of memory.  Linux is designed to use all of the RAM to cache filesystem data, setting min_free_kbytes higher than that will cause the system to spend all of its time reclaiming memory.

4.) drop_caches
    Is this the right parameter to use with page cache and slab cache? The pagecache parameter doesn't seem to exist any more. 

/sys/proc/vm/drop_caches does exist in RHEL6.  

"echo 1 > /proc/sys/vm/drop_caches" will cause to the system to invalidate and free all pagecache memory.

"echo 2 > /proc/sys/vm/drop_caches" will cause the system to free all unused slabcache memory.

"echo 3 > /proc/sys/vm/drop_caches" cause the system to free both pagecache and slabcache memory.

The use of /proc/sys/vm/slabcache should be limited to freeinf memory between benchmarking runs and should not be used in a production environment.


Larry

Comment 8 Larry Woodman 2011-08-23 18:18:31 UTC
ACK to the VM tuning chapter.

Larry


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