Bug 639794
| Summary: | Performance Tuning Guide: TRACKING BUG for [MEMORY] [Capacity Tuning] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Don Domingo <ddomingo> |
| Component: | doc-Performance_Tuning_Guide | Assignee: | Laura Bailey <lbailey> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | ecs-bugs |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.2 | CC: | lwoodman, pkennedy |
| Target Milestone: | rc | Keywords: | Documentation, Tracking |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-10-31 01:08:00 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 639779 | ||
| Deadline: | 2011-07-22 | ||
ACK to the capacity tuning chapter. Larry |
1.) max_map_count Defines the maximum number of memory map areas that a process may use. In most cases, the default value of 65536 is appropriate. When is it not appropriate? Some large applications need to mmap() more than 65536 files. If this is the case appplication will fail the mmap so the sysadmin should increase max_map_count by doubling its current value. 2.) aio-max-nr This parameter is not in the deployment guide. Is it supported? Yes, aio-max-nr is still set to 65536 by default and still defines the maximum allowed number of events in all active asynchronous I/O contexts. Larry