Performance Tuning Guide
Optimizing subsystem throughput in Red Hat Enterprise Linux 6
Chapter 1. Overview
1.1. How to read this book
- Each subsystem chapter describes performance features unique to (or implemented differently in) Red Hat Enterprise Linux 6. These chapters also discuss Red Hat Enterprise Linux 6 updates that significantly improved the performance of specific subsystems over Red Hat Enterprise Linux 5.
- The book also enumerates performance indicators for each specific subsystem. Typical values for these indicators are described in the context of specific services, helping you understand their significance in real-world, production systems.In addition, the Performance Tuning Guide also shows different ways of retrieving performance data (that is, profiling) for a subsystem. Note that some of the profiling tools showcased here are documented elsewhere with more detail.
- Perhaps the most important information in this book are instructions on how to adjust the performance of a specific subsystem in Red Hat Enterprise Linux 6. The Performance Tuning Guide explains how to fine-tune a Red Hat Enterprise Linux 6 subsystem for specific services.
- System/Business Analyst
- This book enumerates and explains Red Hat Enterprise Linux 6 performance features at a high level, providing enough information on how subsystems perform for specific workloads (both by default and when optimized). The level of detail used in describing Red Hat Enterprise Linux 6 performance features helps potential customers and sales engineers understand the suitability of this platform in providing resource-intensive services at an acceptable level.The Performance Tuning Guide also provides links to more detailed documentation on each feature whenever possible. At that detail level, readers can understand these performance features enough to form a high-level strategy in deploying and optimizing Red Hat Enterprise Linux 6. This allows readers to both develop and evaluate infrastructure proposals.This feature-focused level of documentation is suitable for readers with a high-level understanding of Linux subsystems and enterprise-level networks.
- System Administrator
- The procedures enumerated in this book are suitable for system administrators with RHCE  skill level (or its equivalent, that is, 3-5 years experience in deploying and managing Linux). The Performance Tuning Guide aims to provide as much detail as possible about the effects of each configuration; this means describing any performance trade-offs that may occur.The underlying skill in performance tuning lies not in knowing how to analyze and tune a subsystem. Rather, a system administrator adept at performance tuning knows how to balance and optimize a Red Hat Enterprise Linux 6 system for a specific purpose. This means also knowing which trade-offs and performance penalties are acceptable when attempting to implement a configuration designed to boost a specific subsystem's performance.
1.2. Release overview
1.2.1. New features in Red Hat Enterprise Linux 6
1.2.2. Horizontal Scalability
22.214.171.124. Parallel Computing
1.2.3. Distributed Systems
- Horizontal scalability requires many tasks to be performed simultaneously (in parallel). As such, these tasks must have interprocess communication to coordinate their work. Further, a platform with horizontal scalability should be able to share tasks across multiple systems.
- Storage via local disks is not sufficient in addressing the requirements of horizontal scalability. Some form of distributed or shared storage is needed, one with a layer of abstraction that allows a single storage volume's capacity to grow seamlessly with the addition of new storage hardware.
- The most important duty in distributed computing is the management layer. This management layer coordinates all software and hardware components, efficiently managing communication, storage, and the usage of shared resources.
The most common way of communicating between computers is over Ethernet. Today, Gigabit Ethernet (GbE) is provided by default on systems, and most servers include 2-4 ports of Gigabit Ethernet. GbE provides good bandwidth and latency. This is the foundation of most distributed systems in use today. Even when systems include faster network hardware, it is still common to use GbE for a dedicated management interface.
Ten Gigabit Ethernet (10GbE) is rapidly growing in acceptance for high end and even mid-range servers. 10GbE provides ten times the bandwidth of GbE. One of its major advantages is with modern multi-core processors, where it restores the balance between communication and computing. You can compare a single core system using GbE to an eight core system using 10GbE. Used in this way, 10GbE is especially valuable for maintaining overall system performance and avoiding communication bottlenecks.
Infiniband offers even higher performance than 10GbE. In addition to TCP/IP and UDP network connections used with Ethernet, Infiniband also supports shared memory communication. This allows Infiniband to work between systems via remote direct memory access (RDMA).
RDMA over Converged Ethernet (RoCE) implements Infiniband-style communications (including RDMA) over a 10GbE infrastructure. Given the cost improvements associated with the growing volume of 10GbE products, it is reasonable to expect wider usage of RDMA and RoCE in a wide range of systems and applications.
- Multiple systems storing data in a single location
- A storage unit (e.g. a volume) composed of multiple storage appliances
Network File System (NFS) allows multiple servers or users to mount and use the same instance of remote storage via TCP or UDP. NFS is commonly used to hold data shared by multiple applications. It is also convenient for bulk storage of large amounts of data.
Storage Area Networks (SANs) use either Fibre Channel or iSCSI protocol to provide remote access to storage. Fibre Channel infrastructure (such as Fibre Channel host bus adapters, switches, and storage arrays) combines high performance, high bandwidth, and massive storage. SANs separate storage from processing, providing considerable flexibility in system design.
- Controlling access to storage
- Managing large amounts of data
- Provisioning systems
- Backing up and replicating data
- Taking snapshots
- Supporting system failover
- Ensuring data integrity
- Migrating data
The Red Hat Global File System 2 (GFS2) file system provides several specialized capabilities. The basic function of GFS2 is to provide a single file system, including concurrent read/write access, shared across multiple members of a cluster. This means that each member of the cluster sees exactly the same data "on disk" in the GFS2 filesystem.
126.96.36.199. Converged Networks
With FCoE, standard fibre channel commands and data packets are transported over a 10GbE physical infrastructure via a single converged network adapter (CNA). Standard TCP/IP ethernet traffic and fibre channel storage operations can be transported via the same link. FCoE uses one physical network interface card (and one cable) for multiple logical network/storage connections.
- Reduced number of connections
- FCoE reduces the number of network connections to a server by half. You can still choose to have multiple connections for performance or availability; however, a single connection provides both storage and network connectivity. This is especially helpful for pizza box servers and blade servers, since they both have very limited space for components.
- Lower cost
- Reduced number of connections immediately means reduced number of cables, switches, and other networking equipment. Ethernet's history also features great economies of scale; the cost of networks drops dramatically as the number of devices in the market goes from millions to billions, as was seen in the decline in the price of 100Mb Ethernet and gigabit Ethernet devices.Similarly, 10GbE will also become cheaper as more businesses adapt to its use. Also, as CNA hardware is integrated into a single chip, widespread use will also increase its volume in the market, which will result in a significant price drop over time.
Internet SCSI (iSCSI) is another type of converged network protocol; it is an alternative to FCoE. Like fibre channel, iSCSI provides block-level storage over a network. However, iSCSI does not provide a complete management environment. The main advantage of iSCSI over FCoE is that iSCSI provides much of the capability and flexibility of fibre channel, but at a lower cost.
Chapter 2. Red Hat Enterprise Linux 6 Performance Features
2.1. 64-Bit Support
- Huge pages and transparent huge pages
- Non-Uniform Memory Access improvements
The implementation of huge pages in Red Hat Enterprise Linux 6 allows the system to manage memory use efficiently across different memory workloads. Huge pages dynamically utilize 2 MB pages compared to the standard 4 KB page size, allowing applications to scale well while processing gigabytes and even terabytes of memory.
Many new systems now support Non-Uniform Memory Access (NUMA). NUMA simplifies the design and creation of hardware for large systems; however, it also adds a layer of complexity to application development. For example, NUMA implements both local and remote memory, where remote memory can take several times longer to access than local memory. This feature has performance implications for operating systems and applications, and should be configured carefully.
2.2. Ticket Spinlocks
2.3. Dynamic List Structure
2.4. Tickless Kernel
2.5. Control Groups
- A list of tasks assigned to the cgroup
- Resources allocated to those tasks
- Network (bandwidth)
2.6. Storage and File System Improvements
Ext4 is the default file system for Red Hat Enterprise Linux 6. It is the fourth generation version of the EXT file system family, supporting a theoretical maximum file system size of 1 exabyte, and single file maximum size of 16TB. Red Hat Enterprise Linux 6 supports a maximum file system size of 16TB, and a single file maximum size of 16TB. Other than a much larger storage capacity, ext4 also includes several new features, such as:
- Extent-based metadata
- Delayed allocation
- Journal check-summing
XFS is a robust and mature 64-bit journaling file system that supports very large files and file systems on a single host. This file system was originally developed by SGI, and has a long history of running on extremely large servers and storage arrays. XFS features include:
- Delayed allocation
- Dynamically-allocated inodes
- B-tree indexing for scalability of free space management
- Online defragmentation and file system growing
- Sophisticated metadata read-ahead algorithms
Traditional BIOS supports a maximum disk size of 2.2TB. Red Hat Enterprise Linux 6 systems using BIOS can support disks larger than 2.2TB by using a new disk structure called Global Partition Table (GPT). GPT can only be used for data disks; it cannot be used for boot drives with BIOS; therefore, boot drives can only be a maximum of 2.2TB in size. The BIOS was originally created for the IBM PC; while BIOS has evolved considerably to adapt to modern hardware, Unified Extensible Firmware Interface (UEFI) is designed to support new and emerging hardware.
Chapter 3. Monitoring and Analyzing System Performance
3.1. The proc File System
proc"file system" is a directory that contains a hierarchy of files that represent the current state of the Linux kernel. It allows applications and users to see the kernel's view of the system.
procdirectory also contains information about the hardware of the system, and any currently running processes. Most of these files are read-only, but some files (primarily those in
/proc/sys) can be manipulated by users and applications to communicate configuration changes to the kernel.
procdirectory, see the Deployment Guide, available at http://access.redhat.com/site/documentation/Red_Hat_Enterprise_Linux/.
3.2. GNOME and KDE System Monitors
The GNOME System Monitor displays basic system information and allows you to monitor system processes, and resource or file system usage. Open it with the
gnome-system-monitor command in the Terminal, or click on the menu, and select > .
- Displays basic information about the computer's hardware and software.
- Shows active processes, and the relationships between those processes, as well as detailed information about each process. It also lets you filter the processes displayed, and perform certain actions on those processes (start, stop, kill, change priority, etc.).
- Displays the current CPU time usage, memory and swap space usage, and network usage.
- Lists all mounted file systems alongside some basic information about each, such as the file system type, mount point, and memory usage.
The KDE System Guard allows you to monitor current system load and processes that are running. It also lets you perform actions on processes. Open it with the
ksysguard command in the Terminal, or click on the and select > > .
- Displays a list of all running processes, alphabetically by default. You can also sort processes by a number of other properties, including total CPU usage, physical or shared memory usage, owner, and priority. You can also filter the visible results, search for specific processes, or perform certain actions on a process.
- Displays historical graphs of CPU usage, memory and swap space usage, and network usage. Hover over the graphs for detailed analysis and graph keys.
3.3. Performance Co-Pilot (PCP)
pmcd) is responsible for collecting performance data on the host system, and various client tools, such as
pmstat, can be used to retrieve, display, archive, and process this data on the same host or over the network. The pcp package provides the command-line tools and underlying functionality. The graphical tool also requires the pcp-gui package.
- For information on PCP, see the Index of Performance Co-Pilot (PCP) articles, solutions, tutorials and white papers on the Red Hat Customer Portal.
- The manual page named PCPIntro serves as an introduction to Performance Co-Pilot. It provides a list of available tools as well as a description of available configuration options and a list of related manual pages. By default, comprehensive documentation is installed in the
/usr/share/doc/pcp-doc/directory, notably the Performance Co-Pilot User's and Administrator's Guide and Performance Co-Pilot Programmer's Guide.
- If you need to determine what PCP tool has the functionality of an older tool you are already familiar with, see the Side-by-side comparison of PCP tools with legacy tools Red Hat Knowledgebase article.
Overview of System Services and Tools Provided by PCP
Table 3.1. System Services Distributed with Performance Co-Pilot in Red Hat Enterprise Linux 6
Table 3.2. Tools Distributed with Performance Co-Pilot in Red Hat Enterprise Linux 6
- Sets the number of CPUs that can idle before a CPU is placed into powersave mode. If more CPUs than the threshold are more than 1 standard deviation below the average softirq workload and no CPUs are more than one standard deviation above the average, and have more than one irq assigned to them, a CPU is placed into powersave mode. In powersave mode, a CPU is not part of irq balancing so that it is not woken unnecessarily.
- Determines how irq kernel affinity hinting is handled. Valid values are
exact(irq affinity hint is always applied),
subset(irq is balanced, but the assigned object is a subset of the affinity hint), or
ignore(irq affinity hint is ignored completely).
- Defines the location of a script to execute for each interrupt request, with the device path and irq number passed as arguments, and a zero exit code expected by irqbalance. The script defined can specify zero or more key value pairs to guide irqbalance in managing the passed irq.The following are recognized as valid key value pairs.
- Valid values are
true(exclude the passed irq from balancing) or
false(perform balancing on this irq).
- Allows user override of the balance level of the passed irq. By default the balance level is based on the PCI device class of the device that owns the irq. Valid values are
- Allows user override of the NUMA node that is considered local to the passed irq. If information about the local node is not specified in ACPI, devices are considered equidistant from all nodes. Valid values are integers (starting from 0) that identify a specific NUMA node, and
-1, which specifies that an irq should be considered equidistant from all nodes.
- The interrupt with the specified interrupt request number is added to the list of banned interrupts.
IRQBALANCE_BANNED_CPUSenvironment variable to specify a mask of CPUs that are ignored by irqbalance.
$ man irqbalance
3.5. Built-in Command-line Monitoring Tools
12:00:01 AM CPU %user %nice %system %iowait %steal %idle 12:10:01 AM all 0.10 0.00 0.15 2.96 0.00 96.79 12:20:01 AM all 0.09 0.00 0.13 3.16 0.00 96.61 12:30:01 AM all 0.09 0.00 0.14 2.11 0.00 97.66 ...
3.5.1. Getting Information about Pages paged in and Pages paged out
vmstatutility and the
sarutility to get the information about
Pages paged in(PGPGIN) and
Pages paged out(PGPGOUT).
Pages paged inare the blocks of data recorded to the memory.
Pages paged outare the blocks of data recorded from the memory.
vmstat, use the
/proc/vmstatfile on the lines beginning with
- PGPGIN are the blocks of data recorded from any location to the memory
- PGPGOUT are the blocks of data recorded from the memory to any location
sar, use the
- PGPGIN are the blocks of data recorded from disks to the memory
- PGPGOUT are the blocks of data recorded from the memory to disks
ddis the day in the month. For example, you can choose to get the average values for all 10-minute periods from the system start to the current moment. The resulting values are in kilobytes per second.
3.6. Tuned and ktune
- The default power-saving profile. This is the most basic power-saving profile. It enables only the disk and CPU plug-ins. Note that this is not the same as turning tuned-adm off, where both tuned and ktune are disabled.
- A server profile for typical latency performance tuning. This profile disables dynamic tuning mechanisms and transparent hugepages. It uses the
performancegoverner for p-states through
cpuspeed, and sets the I/O scheduler to
deadline. Additionally, in Red Hat Enterprise Linux 6.5 and later, the profile requests a
1. In Red Hat Enterprise Linux 6.4 and earlier,
cpu_dma_latencyrequested a value of
- A server profile for typical throughput performance tuning. This profile is recommended if the system does not have enterprise-class storage. throughput-performance disables power saving mechanisms and enables the
deadlineI/O scheduler. The CPU governor is set to
kernel.sched_min_granularity_ns(scheduler minimal preemption granularity) is set to
kernel.sched_wakeup_granularity_ns(scheduler wake-up granularity) is set to
vm.dirty_ratio(virtual memory dirty ratio) is set to 40%, and transparent huge pages are enabled.
- This profile is recommended for enterprise-sized server configurations with enterprise-class storage, including battery-backed controller cache protection and management of on-disk cache. It is the same as the
throughput-performanceprofile, with one addition: file systems are re-mounted with
- This profile is optimized for virtual machines. It is based on the
enterprise-storageprofile, but also decreases the swappiness of virtual memory. This profile is available in Red Hat Enterprise Linux 6.3 and later.
- Based on the
virtual-hostdecreases the swappiness of virtual memory and enables more aggressive writeback of dirty pages. Non-root and non-boot file systems are mounted with
barrier=0. Additionally, as of Red Hat Enterprise Linux 6.5, the
kernel.sched_migration_costparameter is set to
5milliseconds. Prior to Red Hat Enterprise Linux 6.5,
kernel.sched_migration_costused the default value of
0.5milliseconds. This profile is available in Red Hat Enterprise Linux 6.3 and later.
3.7. Application Profilers
Network monitoring scripts (in
- Every 5 seconds, prints a list of processes (process identifier and command) with the number of packets sent and received and the amount of data sent and received by the process during that interval.
- Instruments each of the functions in the Linux kernel's
net/socket.cfile, and prints trace data.
- Prints information for each new incoming TCP connection accepted by the system. The information includes the UID, the command accepting the connection, the process identifier of the command, the port the connection is on, and the IP address of the originator of the request.
- Every 5 seconds, prints the number of socket buffers freed at locations in the kernel. Use the
--all-modulesoption to see symbolic names.
Storage monitoring scripts (in
- Checks the status of reading/writing disk every 5 seconds and outputs the top ten entries during that period.
- Prints the amount of time spent on read and write operations, and the number of bytes read and written.
- Prints the top ten executables based on cumulative I/O traffic observed, every second.
- Prints the executable name and process identifier as reads and writes to the specified device occur.
- Prints the executable name and process identifier each time a read or write occurs to the specified inode on the specified major/minor device.
- Prints the executable name, process identifier, and attributes each time the attributes are changed on the specified inode on the specified major/minor device.
latencytap.stpscript records the effect that different types of latency have on one or more processes. It prints a list of latency types every 30 seconds, sorted in descending order by the total time the process or processes spent waiting. This can be useful for identifying the cause of both storage and network latency. Red Hat recommends using the
--all-modulesoption with this script to better enable the mapping of latency events. By default, this script is installed to the
- Performance monitoring samples may not be precise - because the processor may execute instructions out of order, a sample may be recorded from a nearby instruction, instead of the instruction that triggered the interrupt.
- Because OProfile is system-wide and expects processes to start and stop multiple times, samples from multiple runs are allowed to accumulate. This means you may need to clear sample data from previous runs.
- It focuses on identifying problems with CPU-limited processes, and therefore does not identify processes that are sleeping while they wait on locks for other events.
man valgrindcommand when the valgrind package is installed. Accompanying documentation can also be found in:
- This command provides overall statistics for common performance events, including instructions executed and clock cycles consumed. You can use the option flags to gather statistics on events other than the default measurement events. As of Red Hat Enterprise Linux 6.4, it is possible to use
perf statto filter monitoring based on one or more specified control groups (cgroups). For further information, read the man page:
- This command records performance data into a file which can be later analyzed using
perf report. For further details, read the man page:
man perf-record.As of Red Hat Enterprise Linux 6.6, the
-joptions are provided to allow statistical sampling of taken branches. The
-boption samples any branches taken, while the
-joption can be adjusted to sample branches of different types, such as user level or kernel level branches.
- This command reads the performance data from a file and analyzes the recorded data. For further details, read the man page:
- This command lists the events available on a particular machine. These events will vary based on the performance monitoring hardware and the software configuration of the system. For further information, read the man page:
- Available as of Red Hat Enterprise Linux 6.6. This command profiles the frequency of each type of memory access operation performed by a specified application or command. This allows a user to see the frequency of load and store operations performed by the profiled application. For further information, read the man page:
- This command performs a similar function to the top tool. It generates and displays a performance counter profile in realtime. For further information, read the man page:
- This command performs a similar function to the strace tool. It monitors the system calls used by a specified thread or process and all signals received by that application. Additional trace targets are available; refer to the man page for a full list.
3.8. Red Hat Enterprise MRG
- BIOS parameters related to power management, error detection, and system management interrupts;
- network settings, such as interrupt coalescing, and the use of TCP;
- journaling activity in journaling file systems;
- system logging;
- whether interrupts and user processes are handled by a specific CPU or range of CPUs;
- whether swap space is used; and
- how to deal with out-of-memory exceptions.
Chapter 4. CPU
4.1. CPU Topology
4.1.1. CPU and NUMA Topology
- Serial buses
- NUMA topologies
- What is the topology of the system?
- Where is the application currently executing?
- Where is the closest memory bank?
4.1.2. Tuning CPU Performance
- A CPU (any of 0-3) presents the memory address to the local memory controller.
- The memory controller sets up access to the memory address.
- The CPU performs read or write operations on that memory address.
Figure 4.1. Local and Remote Memory Access in NUMA Topology
- A CPU (any of 0-3) presents the remote memory address to the local memory controller.
- The CPU's request for that remote memory address is passed to a remote memory controller, local to the node containing that memory address.
- The remote memory controller sets up access to the remote memory address.
- The CPU performs read or write operations on that remote memory address.
- the topology of the system (how its components are connected),
- the core on which the application executes, and
- the location of the closest memory bank.
188.8.131.52. Setting CPU Affinity with taskset
0x00000001represents processor 0, and
0x00000003represents processors 0 and 1.
# taskset -p mask pid
# taskset mask -- program
-coption to provide a comma-delimited list of separate processors, or a range of processors, like so:
# taskset -c 0,5,7-9 -- myprogram
184.108.40.206. Controlling NUMA Policy with numactl
numactlruns processes with a specified scheduling or memory placement policy. The selected policy is set for that process and all of its children.
numactlcan also set a persistent policy for shared memory segments or files, and set the CPU affinity and memory affinity of a process. It uses the
/sysfile system to determine system topology.
/sysfile system contains information about how CPUs, memory, and peripheral devices are connected via NUMA interconnects. Specifically, the
/sys/devices/system/cpudirectory contains information about how a system's CPUs are connected to one another. The
/sys/devices/system/nodedirectory contains information about the NUMA nodes in the system, and the relative distances between those nodes.
- Display the NUMA policy settings of the current process. This parameter does not require further parameters, and can be used like so:
- Displays an inventory of the available nodes on the system.
- Only allocate memory from the specified nodes. When this is in use, allocation will fail if memory on these nodes is insufficient. Usage for this parameter is
numactl --membind=nodes program, where nodes is the list of nodes you want to allocate memory from, and program is the program whose memory requirements should be allocated from that node. Node numbers can be given as a comma-delimited list, a range, or a combination of the two. Further details are available on the numactl man page:
- Only execute a command (and its child processes) on CPUs belonging to the specified node(s). Usage for this parameter is
numactl --cpunodebind=nodes program, where nodes is the list of nodes to whose CPUs the specified program (program) should be bound. Node numbers can be given as a comma-delimited list, a range, or a combination of the two. Further details are available on the numactl man page:
- Only execute a command (and its child processes) on the specified CPUs. Usage for this parameter is
numactl --physcpubind=cpu program, where cpu is a comma-delimited list of physical CPU numbers as displayed in the processor fields of
/proc/cpuinfo, and program is the program that should execute only on those CPUs. CPUs can also be specified relative to the current
cpuset. Refer to the numactl man page for further information:
- Specifies that memory should always be allocated on the current node.
- Where possible, memory is allocated on the specified node. If memory cannot be allocated on the node specified, fall back to other nodes. This option takes only a single node number, like so:
numactl --preferred=node. Refer to the numactl man page for further information:
4.1.3. Hardware performance policy (x86_energy_perf_policy)
x86_energy_perf_policyrequires root privileges, and operates on all CPUs by default.
# x86_energy_perf_policy -r
# x86_energy_perf_policy profile_name
- The processor is unwilling to sacrifice any performance for the sake of saving energy. This is the default value.
- The processor tolerates minor performance compromises for potentially significant energy savings. This is a reasonable setting for most desktops and servers.
- The processor accepts potentially significant hits to performance in order to maximise energy efficiency.
rootprivileges to run. It also requires processor support for invariant time stamp counters, and APERF and MPERF model-specific registers.
- The processor package number.
- The processor core number.
- The Linux CPU (logical processor) number.
- The percentage of the interval for which the CPU retired instructions.
- The average clock speed while the CPU was in the c0 state. When this number is higher than the value in TSC, the CPU is in turbo mode.
- The average clock speed over the course of the entire interval. When this number is lower than the value in TSC, the CPU is in turbo mode.
- %c1, %c3, and %c6
- The percentage of the interval for which the processor was in the c1, c3, or c6 state, respectively.
- %pc3 or %pc6
- The percentage of the interval for which the processor was in the pc3 or pc6 state, respectively.
-ioption, for example, run
turbostat -i 10to print results every 10 seconds instead.
numastat, with no options or parameters) maintains strict compatibility with the previous version of the tool, note that supplying options or parameters to this command significantly changes both the output content and its format.
numastatdisplays how many pages of memory are occupied by the following event categories for each node.
Default Tracking Categories
- The number of attempted allocations to this node that were successful.
- The number of attempted allocations to another node that were allocated on this node because of low memory on the intended node. Each
numa_missevent has a corresponding
numa_foreignevent on another node.
- The number of allocations initially intended for this node that were allocated to another node instead. Each
numa_foreignevent has a corresponding
numa_missevent on another node.
- The number of attempted interleave policy allocations to this node that were successful.
- The number of times a process on this node successfully allocated memory on this node.
- The number of times a process on another node allocated memory on this node.
- Horizontally condenses the displayed table of information. This is useful on systems with a large number of NUMA nodes, but column width and inter-column spacing are somewhat unpredictable. When this option is used, the amount of memory is rounded to the nearest megabyte.
- Displays system-wide memory usage information on a per-node basis, similar to the information found in
- Displays the same information as the original
numastatcommand (numa_hit, numa_miss, numa_foreign, interleave_hit, local_node, and other_node), with an updated format, using megabytes as the unit of measurement.
- Displays per-node memory information for the specified pattern. If the value for pattern is comprised of digits, numastat assumes that it is a numerical process identifier. Otherwise, numastat searches process command lines for the specified pattern.Command line arguments entered after the value of the
-poption are assumed to be additional patterns for which to filter. Additional patterns expand, rather than narrow, the filter.
- Sorts the displayed data in descending order so that the biggest memory consumers (according to the
totalcolumn) are listed first.Optionally, you can specify a node, and the table will be sorted according to the node column. When using this option, the node value must follow the
-soption immediately, as shown here:
numastat -s2Do not include white space between the option and its value.
- Displays more verbose information. Namely, process information for multiple processes will display detailed information for each process.
- Displays numastat version information.
- Omits table rows and columns with only zero values from the displayed information. Note that some near-zero values that are rounded to zero for display purposes will not be omitted from the displayed output.
4.1.6. NUMA Affinity Management Daemon (numad)
/procfile system to monitor available system resources on a per-node basis. The daemon then attempts to place significant processes on NUMA nodes that have sufficient aligned memory and CPU resources for optimum NUMA performance. Current thresholds for process management are at least 50% of one CPU and at least 300 MB of memory. numad attempts to maintain a resource utilization level, and rebalances allocations when necessary by moving processes between NUMA nodes.
-woption for pre-placement advice:
220.127.116.11. Benefits of numad
18.104.22.168. Modes of operation
0to avoid merging pages across NUMA nodes. Kernel memory accounting statistics can eventually contradict each other after large amounts of cross-node merging. As such,
numadcan become confused after the KSM daemon merges large amounts of memory. If your system has a large amount of free memory, you may achieve higher performance by turning off and disabling the KSM daemon.
- as a service
- as an executable
22.214.171.124.1. Using numad as a service
# service numad start
# chkconfig numad on
126.96.36.199.2. Using numad as an executable
# numad -S 0 -p pid
- Adds the specified pid to an explicit inclusion list. The process specified will not be managed until it meets the numad process significance threshold.
-Sparameter specifies the type of process scanning. Setting it to
0as shown limits numad management to explicitly included processes.
# numad -i 0
4.1.7. Dynamic Resource Affinity on Power Architecture
ppc64-diagpackages process the event and update the system with the new CPU or memory affinity information.
4.2. CPU Scheduling
- Realtime policies
- Normal policies
4.2.1. Realtime scheduling policies
- This policy is also referred to as static priority scheduling, because it defines a fixed priority (between 1 and 99) for each thread. The scheduler scans a list of SCHED_FIFO threads in priority order and schedules the highest priority thread that is ready to run. This thread runs until it blocks, exits, or is preempted by a higher priority thread that is ready to run.Even the lowest priority realtime thread will be scheduled ahead of any thread with a non-realtime policy; if only one realtime thread exists, the
SCHED_FIFOpriority value does not matter.
- A round-robin variant of the
SCHED_RRthreads are also given a fixed priority between 1 and 99. However, threads with the same priority are scheduled round-robin style within a certain quantum, or time slice. The
sched_rr_get_interval(2)system call returns the value of the time slice, but the duration of the time slice cannot be set by a user. This policy is useful if you need multiple thread to run at the same priority.
SCHED_FIFOthreads run until they block, exit, or are pre-empted by a thread with a higher priority. Setting a priority of 99 is therefore not recommended, as this places your process at the same priority level as migration and watchdog threads. If these threads are blocked because your thread goes into a computational loop, they will not be able to run. Uniprocessor systems will eventually lock up in this situation.
SCHED_FIFOpolicy includes a bandwidth cap mechanism. This protects realtime application programmers from realtime tasks that might monopolize the CPU. This mechanism can be adjusted through the following
/procfile system parameters:
- Defines the time period to be considered one hundred percent of CPU bandwidth, in microseconds ('us' being the closest equivalent to 'µs' in plain text). The default value is 1000000µs, or 1 second.
- Defines the time period to be devoted to running realtime threads, in microseconds ('us' being the closest equivalent to 'µs' in plain text). The default value is 950000µs, or 0.95 seconds.
4.2.2. Normal scheduling policies
SCHED_IDLE. However, the
SCHED_IDLEpolicies are intended for very low priority jobs, and as such are of limited interest in a performance tuning guide.
- The default scheduling policy. This policy uses the Completely Fair Scheduler (CFS) to provide fair access periods for all threads using this policy. CFS establishes a dynamic priority list partly based on the
nicenessvalue of each process thread. (Refer to the Deployment Guide for more details about this parameter and the
/procfile system.) This gives users some indirect level of control over process priority, but the dynamic priority list can only be directly changed by the CFS.
4.2.3. Policy Selection
SCHED_OTHERand let the system manage CPU utilization for you.
SCHED_FIFO. If you have a small number of threads, consider isolating a CPU socket and moving your threads onto that socket's cores so that there are no other threads competing for time on the cores.
4.3. Interrupts and IRQ Tuning
/proc/interruptsfile lists the number of interrupts per CPU per I/O device. It displays the IRQ number, the number of that interrupt handled by each CPU core, the interrupt type, and a comma-delimited list of drivers that are registered to receive that interrupt. (Refer to the proc(5) man page for further details:
man 5 proc)
smp_affinity, which defines the CPU cores that are allowed to execute the ISR for that IRQ. This property can be used to improve application performance by assigning both interrupt affinity and the application's thread affinity to one or more specific CPU cores. This allows cache line sharing between the specified interrupt and application threads.
/proc/irq/IRQ_NUMBER/smp_affinityfile, which can be viewed and modified by the root user. The value stored in this file is a hexadecimal bit-mask representing all CPU cores in the system.
# grep eth0 /proc/interrupts 32: 0 140 45 850264 PCI-MSI-edge eth0
# cat /proc/irq/32/smp_affinity f
f, meaning that the IRQ can be serviced on any of the CPUs in the system. Setting this value to
1, as follows, means that only CPU 0 can service this interrupt:
# echo 1 >/proc/irq/32/smp_affinity # cat /proc/irq/32/smp_affinity 1
smp_affinityvalues for discrete 32-bit groups. This is required on systems with more than 32 cores. For example, the following example shows that IRQ 40 is serviced on all cores of a 64-core system:
# cat /proc/irq/40/smp_affinity ffffffff,ffffffff
# echo 0xffffffff,00000000 > /proc/irq/40/smp_affinity # cat /proc/irq/40/smp_affinity ffffffff,00000000
smp_affinityof an IRQ sets up the hardware so that the decision to service an interrupt with a particular CPU is made at the hardware level, with no intervention from the kernel.
4.4. CPU Frequency Governors
cpufreqgovernors determine the frequency of a CPU at any given time based on a set of rules about the kind of behavior that prompts a change to a higher or lower frequency.
cpufreq_ondemandgovernor for most situations, as this governor provides better performance through a higher CPU frequency when the system is under load, and power savings through a lower CPU frequency when the system is not being heavily used.
io_is_busy. If this is set to
1, Input/Output (I/O) activity is included in CPU activity calculations, and if set to
0it is excluded. The default setting is
1. If I/O activity is excluded, the
ondemandgovernor may reduce the CPU frequency to reduce power usage, resulting in slower I/O operations.
cpufreq_performancegovernor. This governor uses the highest possible CPU frequency to ensure that tasks execute as quickly as possible. This governor does not make use of power saving mechanisms such as sleep or idle, and is therefore not recommended for data centers or similar large deployments.
Procedure 4.1. Enabling and configuring a governor
- Ensure that cpupowerutils is installed:
# yum install cpupowerutils
- Check that the driver you want to use is available.
# cpupower frequency-info --governors
- If the driver you want is not available, use the
modprobecommand to add it to your system. For example, to add the
# modprobe cpufreq_ondemand
- Set the governor temporarily by using the cpupower command line tool. For example, to set the
# cpupower frequency-set --governor ondemand
4.5. Enhancements to NUMA in Red Hat Enterprise Linux 6
4.5.1. Bare-metal and Scalability Optimizations
188.8.131.52. Enhancements in topology-awareness
- enhanced topology detection
- This allows the operating system to detect low-level hardware details (such as logical CPUs, hyper threads, cores, sockets, NUMA nodes and access times between nodes) at boot time, and optimize processing on your system.
- completely fair scheduler
- This new scheduling mode ensures that runtime is shared evenly between eligible processes. Combining this with topology detection allows processes to be scheduled onto CPUs within the same socket to avoid the need for expensive remote memory access, and ensure that cache content is preserved wherever possible.
mallocis now optimized to ensure that the regions of memory that are allocated to a process are as physically close as possible to the core on which the process is executing. This increases memory access speeds.
- skbuff I/O buffer allocation
- Similarly to
malloc, this is now optimized to use memory that is physically close to the CPU handling I/O operations such as device interrupts.
- device interrupt affinity
- Information recorded by device drivers about which CPU handles which interrupts can be used to restrict interrupt handling to CPUs within the same physical socket, preserving cache affinity and limiting high-volume cross-socket communication.
184.108.40.206. Enhancements in Multi-processor Synchronization
- Read-Copy-Update (RCU) locks
- Typically, 90% of locks are acquired for read-only purposes. RCU locking removes the need to obtain an exclusive-access lock when the data being accessed is not being modified. This locking mode is now used in page cache memory allocation: locking is now used only for allocation or deallocation operations.
- per-CPU and per-socket algorithms
- Many algorithms have been updated to perform lock coordination among cooperating CPUs on the same socket to allow for more fine-grained locking. Numerous global spinlocks have been replaced with per-socket locking methods, and updated memory allocator zones and related memory page lists allow memory allocation logic to traverse a more efficient subset of the memory mapping data structures when performing allocation or deallocation operations.
4.5.2. Virtualization Optimizations
- CPU pinning
- Virtual guests can be bound to run on a specific socket in order to optimize local cache use and remove the need for expensive inter-socket communications and remote memory access.
- transparent hugepages (THP)
- With THP enabled, the system automatically performs NUMA-aware memory allocation requests for large contiguous amounts of memory, reducing both lock contention and the number of translation lookaside buffer (TLB) memory management operations required and yielding a performance increase of up to 20% in virtual guests.
- kernel-based I/O implementation
- The virtual guest I/O subsystem is now implemented in the kernel, greatly reducing the expense of inter-node communication and memory access by avoiding a significant amount of context switching, and synchronization and communication overhead.
Chapter 5. Memory
5.1. Huge Translation Lookaside Buffer (HugeTLB)
5.2. Huge Pages and Transparent Huge Pages
- Increase the number of page table entries in the hardware memory management unit
- Increase the page size
5.2.1. Configure Huge Pages
Huge pages kernel options
- Defines the number of persistent huge pages configured in the kernel at boot time. The default value is
0. It is only possible to allocate (or deallocate) huge pages if there are sufficient physically contiguous free pages in the system. Pages reserved by this parameter cannot be used for other purposes.Default size huge pages can be dynamically allocated or deallocated by changing the value of the
/proc/sys/vm/nr_hugepagesfile.In a NUMA system, huge pages assigned with this parameter are divided equally between nodes. You can assign huge pages to specific nodes at runtime by changing the value of the node's
/sys/devices/system/node/node_id/hugepages/hugepages-1048576kB/nr_hugepagesfile.For more information, read the relevant kernel documentation, which is installed in
/usr/share/doc/kernel-doc-kernel_version/Documentation/vm/hugetlbpage.txtby default. This documentation is available only if the kernel-doc package is installed.
- Defines the size of persistent huge pages configured in the kernel at boot time. Valid values are 2 MB and 1 GB. The default value is 2 MB.
- Defines the default size of persistent huge pages configured in the kernel at boot time. Valid values are 2 MB and 1 GB. The default value is 2 MB.
5.3. Using Valgrind to Profile Memory Usage
valgrind --tool=toolname program
cachegrind), and program with the program you wish to profile with Valgrind. Be aware that Valgrind's instrumentation will cause your program to run more slowly than it would normally.
man valgrindcommand when the valgrind package is installed, or found in the following locations:
5.3.1. Profiling Memory Usage with Memcheck
valgrind program, without specifying
--tool=memcheck. It detects and reports on a number of memory errors that can be difficult to detect and diagnose, such as memory access that should not occur, the use of undefined or uninitialized values, incorrectly freed heap memory, overlapping pointers, and memory leaks. Programs run ten to thirty times more slowly with Memcheck than when run normally.
- When enabled, Memcheck searches for memory leaks when the client program finishes. The default value is
summary, which outputs the number of leaks found. Other possible values are
full, both of which give details of each individual leak, and
no, which disables memory leak checking.
- When enabled (set to
yes), Memcheck reports errors when undefined values are used. When disabled (set to
no), undefined value errors are not reported. This is enabled by default. Disabling it speeds up Memcheck slightly.
- Allows the user to specify one or more ranges that Memcheck should ignore when checking for addressability. Multiple ranges are delimited by commas, for example,
5.3.2. Profiling Cache Usage with Cachegrind
# valgrind --tool=cachegrind program
- first-level instruction cache reads (or instructions executed) and read misses, and last-level cache instruction read misses;
- data cache reads (or memory reads), read misses, and last-level cache data read misses;
- data cache writes (or memory writes), write misses, and last-level cache write misses;
- conditional branches executed and mispredicted; and
- indirect branches executed and mispredicted.
cachegrind.out.pidby default, where pid is the process ID of the program on which you ran Cachegrind). This file can be further processed by the accompanying cg_annotate tool, like so:
# cg_annotate cachegrind.out.pid
# cg_diff first second
- Specifies the size, associativity, and line size of the first-level instruction cache, separated by commas:
- Specifies the size, associativity, and line size of the first-level data cache, separated by commas:
- Specifies the size, associativity, and line size of the last-level cache, separated by commas:
- Enables or disables the collection of cache access and miss counts. The default value is
yes(enabled).Note that disabling both this and
--branch-simleaves Cachegrind with no information to collect.
- Enables or disables the collection of branch instruction and misprediction counts. This is set to
no(disabled) by default, since it slows Cachegrind by approximately 25 per-cent.Note that disabling both this and
--cache-simleaves Cachegrind with no information to collect.
5.3.3. Profiling Heap and Stack Space with Massif
massifas the Valgrind tool you wish to use:
# valgrind --tool=massif program
massif.out.pid, where pid is the process ID of the specified program.
ms_printcommand, like so:
# ms_print massif.out.pid
- Specifies whether to perform heap profiling. The default value is
yes. Heap profiling can be disabled by setting this option to
- Specifies the number of bytes per block to use for administration when heap profiling is enabled. The default value is
8bytes per block.
- Specifies whether to perform stack profiling. The default value is
no(disabled). To enable stack profiling, set this option to
yes, but be aware that doing so will greatly slow Massif. Also note that Massif assumes that the main stack has size zero at start-up in order to better indicate the size of the stack portion over which the program being profiled has control.
- Specifies the unit of time used for the profiling. There are three valid values for this option: instructions executed (
i), the default value, which is useful in most cases; real time (
ms, in milliseconds), which can be useful in certain instances; and bytes allocated/deallocated on the heap and/or stack (
B), which is useful for very short-run programs, and for testing purposes, because it is the most reproducible across different machines. This option is useful when graphing Massif output with
5.4. Capacity Tuning
# echo 1 > /proc/sys/vm/overcommit_memory
sysctlcommand. For information on how to use
sysctl, see E.4. Using the sysctl Command in the Red Hat Enterprise Linux 6 Deployment Guide.
/proc/meminfofile provides the
MemAvailablefield. To determine how much memory is available, run:
# cat /proc/meminfo | grep MemAvailable
Capacity-related Memory Tunables
/proc/sys/vm/in the proc file system.
- Defines the conditions that determine whether a large memory request is accepted or denied. There are three possible values for this parameter:
0— The default setting. The kernel performs heuristic memory overcommit handling by estimating the amount of memory available and failing requests that are blatantly invalid. Unfortunately, since memory is allocated using a heuristic rather than a precise algorithm, this setting can sometimes allow available memory on the system to be overloaded.
1— The kernel performs no memory overcommit handling. Under this setting, the potential for memory overload is increased, but so is performance for memory-intensive tasks.
2— The kernel denies requests for memory equal to or larger than the sum of total available swap and the percentage of physical RAM specified in
overcommit_ratio. This setting is best if you want a lesser risk of memory overcommitment.
NoteThis setting is only recommended for systems with swap areas larger than their physical memory.
- Specifies the percentage of physical RAM considered when
overcommit_memoryis set to
2. The default value is
- Defines the maximum number of memory map areas that a process may use. In most cases, the default value of
65530is appropriate. Increase this value if your application needs to map more than this number of files.
- Defines the number of hugepages configured in the kernel. The default value is 0. It is only possible to allocate (or deallocate) hugepages if there are sufficient physically contiguous free pages in the system. Pages reserved by this parameter cannot be used for other purposes. Further information is available from the installed documentation:
/usr/share/doc/kernel-doc-kernel_version/Documentation/vm/hugetlbpage.txt.For an Oracle database workload, Red Hat recommends configuring a number of hugepages equivalent to slightly more than the total size of the system global area of all databases running on the system. 5 additional hugepages per database instance is sufficient.
Capacity-related Kernel Tunables
/proc/sys/kernel/directory, can be calculated by the kernel at boot time depending on available system resources.
# getconf PAGE_SIZE
# grep Hugepagesize /proc/meminfo
- Defines the maximum allowable size in bytes of any single message in a message queue. This value must not exceed the size of the queue (
msgmnb). To determine the current
msgmaxvalue on your system, enter:
# sysctl kernel.msgmax
- Defines the maximum size in bytes of a single message queue. To determine the current
msgmnbvalue on your system, enter:
# sysctl kernel.msgmnb
- Defines the maximum number of message queue identifiers (and therefore the maximum number of queues). To determine the current
msgmnivalue on your system, enter:
# sysctl kernel.msgmni
- Semaphores, counters that help synchronize processes and threads, are generally configured to assist with database workloads. Recommended values vary between databases. See your database documentation for details about semaphore values.This parameter takes four values, separated by spaces, that represent SEMMSL, SEMMNS, SEMOPM, and SEMMNI respectively.
- Defines the total number of shared memory pages that can be used on the system at one time. For database workloads, Red Hat recommends that this value is set to the result of
shmmaxdivided by the hugepage size. However, Red Hat recommends checking your vendor documentation for recommended values. To determine the current
shmallvalue on your system, enter:
- Defines the maximum shared memory segment allowed by the kernel, in bytes. For database workloads, Red Hat recommends a value no larger than 75% of the total memory on the system. However, Red Hat recommends checking your vendor documentation for recommended values. To determine the current
shmmaxvalue on your system, enter:
# sysctl kernel.shmmax
- Defines the system-wide maximum number of shared memory segments. The default value is
4096on all systems.
- Defines the system-wide maximum number of threads (tasks) to be used by the kernel at one time. To determine the current
threads-maxvalue on your system, enter:
# sysctl kernel.threads-maxThe default value is the result of:
mempages / (8 * THREAD_SIZE / PAGE_SIZE )The minimum value of
Capacity-related File System Tunables
/proc/sys/fs/in the proc file system.
- Defines the maximum allowed number of events in all active asynchronous I/O contexts. The default value is
65536. Note that changing this value does not pre-allocate or resize any kernel data structures.
- Lists the maximum number of file handles that the kernel allocates. The default value matches the value of
files_stat.max_filesin the kernel, which is set to the largest value out of either
(mempages * (PAGE_SIZE / 1024)) / 10, or
NR_FILE(8192 in Red Hat Enterprise Linux). Raising this value can resolve errors caused by a lack of available file handles.
Out-of-Memory Kill Tunables
0instructs the kernel to call the
oom_killerfunction when OOM occurs. Usually,
oom_killercan kill rogue processes and the system survives.
oom_killerfunction. It is located under
/proc/pid/in the proc file system, where pid is the process ID number.
- Defines a value from
15that helps determine the
oom_scoreof a process. The higher the
oom_scorevalue, the more likely the process will be killed by the
oom_killer. Setting a
oom_killerfor that process.
ImportantAny processes spawned by an adjusted process will inherit that process's
oom_score. For example, if an
sshdprocess is protected from the
oom_killerfunction, all processes initiated by that SSH session will also be protected. This can affect the
oom_killerfunction's ability to salvage the system if OOM occurs.
5.5. Tuning Virtual Memory
- A value from 0 to 100 which controls the degree to which the system favors anonymous memory or the page cache. A high value improves file-system performance, while aggressively swapping less active processes out of physical memory. A low value avoids swapping processes out of memory, which usually decreases latency, at the cost of I/O performance. The default value is 60.
WarningSince RHEL 6.4, setting
swappiness=0more aggressively avoids swapping out, which increases the risk of OOM killing under strong memory and I/O pressure.A low
swappinessvalue is recommended for database workloads. For example, for Oracle databases, Red Hat recommends a
- The minimum number of kilobytes to keep free across the system. This value is used to compute a watermark value for each low memory zone, which are then assigned a number of reserved free pages proportional to their size.
WarningBe cautious when setting this parameter, as both too-low and too-high values can be damaging and break your system.Setting
min_free_kbytestoo low prevents the system from reclaiming memory. This can result in system hangs and OOM-killing multiple processes.However, setting this parameter to a value that is too high (5-10% of total system memory) will cause your system to become out-of-memory immediately. Linux is designed to use all available RAM to cache file system data. Setting a high
min_free_kbytesvalue results in the system spending too much time reclaiming memory.
- Defines a percentage value. Writeout of dirty data begins (via pdflush) when dirty data comprises this percentage of total system memory. The default value is
20.Red Hat recommends a slightly lower value of
15for database workloads.
- Defines a percentage value. Writeout of dirty data begins in the background (via pdflush) when dirty data comprises this percentage of total memory. The default value is
10. For database workloads, Red Hat recommends a lower value of
- Specifies the number of centiseconds (hundredths of a second) dirty data remains in the page cache before it is eligible to be written back to disk. Red Hat does not recommend tuning this parameter.
- Specifies the length of the interval between kernel flusher threads waking and writing eligible data to disk, in centiseconds (hundredths of a second). Setting this to
0disables periodic write behavior. Red Hat does not recommend tuning this parameter.
- Setting this value to
3causes the kernel to drop various combinations of page cache and slab cache.
This is a non-destructive operation. Since dirty objects cannot be freed, running
- The system invalidates and frees all page cache memory.
- The system frees all unused slab cache memory.
- The system frees all page cache and slab cache memory.
syncbefore setting this parameter's value is recommended.
drop_cachesto free memory is not recommended in a production environment.
# echo 50 > /proc/sys/vm/swappiness
sysctlcommand. For further information, refer to the Deployment Guide, available from http://access.redhat.com/site/documentation/Red_Hat_Enterprise_Linux/.
ksmservice starts and stops the KSM thread, and the
ksmtunedservice controls and tunes the
ksmservice. For information on KSM and its tuning, see the KSM chapter of the Red Hat Enterprise Linux 6 Virtualization Administration Guide.
Chapter 6. Input/Output
- Solid state disks (SSDs) are now recognized automatically, and the performance of the I/O scheduler is tuned to take advantage of the high I/Os per second (IOPS) that these devices can perform. For information on tuning SSDs, see the Solid State Disk Deployment Guidelines chapter in the Red Hat Enterprise Linux 6 Storage Administration Guide.
- Discard support has been added to the kernel to report unused block ranges to the underlying storage. This helps SSDs with their wear-leveling algorithms. It also helps storage that supports logical block provisioning (a sort of virtual address space for storage) by keeping closer tabs on the actual amount of storage in-use.
- The file system barrier implementation was overhauled in Red Hat Enterprise Linux 6.1 to make it more performant.
pdflushhas been replaced by per-backing-device flusher threads, which greatly improves system scalability on configurations with large LUN counts.
Figure 6.1. aio-stress output for 1 thread, 1 file
bo(block out), and
wa(I/O wait time).
soare useful when your swap space is on the same device as your data partition, and as an indicator of overall memory pressure.
biare read operations, while
boare write operations. Each of these categories is reported in kilobytes.
wais idle time; it indicates what portion of the run queue is blocked waiting for I/O complete.
cachecolumns are also worth noting. The
cachevalue increasing alongside the
bovalue, followed by a drop in
cacheand an increase in
freeindicates that the system is performing write-back and invalidation of the page cache.
avgqu-sz), you can make some estimations about how the storage should perform using the graphs you generated when characterizing the performance of your storage. Some generalizations apply: for example, if the average request size is 4KB and the average queue size is 1, throughput is unlikely to be extremely performant.
8,64 3 1 0.000000000 4162 Q RM 73992 + 8 [fs_mark] 8,64 3 0 0.000012707 0 m N cfq4162S / alloced 8,64 3 2 0.000013433 4162 G RM 73992 + 8 [fs_mark] 8,64 3 3 0.000015813 4162 P N [fs_mark] 8,64 3 4 0.000017347 4162 I R 73992 + 8 [fs_mark] 8,64 3 0 0.000018632 0 m N cfq4162S / insert_request 8,64 3 0 0.000019655 0 m N cfq4162S / add_to_rr 8,64 3 0 0.000021945 0 m N cfq4162S / idle=0 8,64 3 5 0.000023460 4162 U N [fs_mark] 1 8,64 3 0 0.000025761 0 m N cfq workload slice:300 8,64 3 0 0.000027137 0 m N cfq4162S / set_active wl_prio:0 wl_type:2 8,64 3 0 0.000028588 0 m N cfq4162S / fifo=(null) 8,64 3 0 0.000029468 0 m N cfq4162S / dispatch_insert 8,64 3 0 0.000031359 0 m N cfq4162S / dispatched a request 8,64 3 0 0.000032306 0 m N cfq4162S / activate rq, drv=1 8,64 3 6 0.000032735 4162 D R 73992 + 8 [fs_mark] 8,64 1 1 0.004276637 0 C R 73992 + 8 
Total (sde): Reads Queued: 19, 76KiB Writes Queued: 142,183, 568,732KiB Read Dispatches: 19, 76KiB Write Dispatches: 25,440, 568,732KiB Reads Requeued: 0 Writes Requeued: 125 Reads Completed: 19, 76KiB Writes Completed: 25,315, 568,732KiB Read Merges: 0, 0KiB Write Merges: 116,868, 467,472KiB IO unplugs: 20,087 Timer unplugs: 0
- Q — A block I/O is Queued
- G — Get RequestA newly queued block I/O was not a candidate for merging with any existing request, so a new block layer request is allocated.
- M — A block I/O is Merged with an existing request.
- I — A request is Inserted into the device's queue.
- D — A request is issued to the Device.
- C — A request is Completed by the driver.
- P — The block device queue is Plugged, to allow the aggregation of requests.
- U — The device queue is Unplugged, allowing the aggregated requests to be issued to the device.
- Q2Q — time between requests sent to the block layer
- Q2G — how long it takes from the time a block I/O is queued to the time it gets a request allocated for it
- G2I — how long it takes from the time a request is allocated to the time it is Inserted into the device's queue
- Q2M — how long it takes from the time a block I/O is queued to the time it gets merged with an existing request
- I2D — how long it takes from the time a request is inserted into the device's queue to the time it is actually issued to the device
- M2D — how long it takes from the time a block I/O is merged with an exiting request until the request is issued to the device
- D2C — service time of the request by the device
- Q2C — total time spent in the block layer for a request
Figure 6.2. Example seekwatcher output
6.4.1. Completely Fair Queuing (CFQ)
ionicecommand, or programmatically assigned via the
ioprio_setsystem call. By default, processes are placed in the best-effort scheduling class. The real-time and best-effort scheduling classes are further subdivided into eight I/O priorities within each class, priority 0 being the highest and 7 the lowest. Processes in the real-time scheduling class are scheduled much more aggressively than processes in either best-effort or idle, so any scheduled real-time I/O is always performed before best-effort or idle I/O. This means that real-time priority I/O can starve out both the best-effort and idle classes. Best effort scheduling is the default scheduling class, and 4 is the default priority within this class. Processes in the idle scheduling class are only serviced when there is no other I/O pending in the system. Thus, it is very important to only set the I/O scheduling class of a process to idle if I/O from the process is not at all required for making forward progress.
slice_idle = 0 quantum = 64 group_idle = 1
group_idleis set to 1, there is still the potential for I/O stalls (whereby the back-end storage is not busy due to idling). However, these stalls will be less frequent than idling on every queue in the system.
- Backward seeks are typically bad for performance, as they can incur greater delays in repositioning the heads than forward seeks do. However, CFQ will still perform them, if they are small enough. This tunable controls the maximum distance in KB the I/O scheduler will allow backward seeks. The default is
- Because of the inefficiency of backward seeks, a penalty is associated with each one. The penalty is a multiplier; for example, consider a disk head position at 1024KB. Assume there are two requests in the queue, one at 1008KB and another at 1040KB. The two requests are equidistant from the current head position. However, after applying the back seek penalty (default: 2), the request at the later position on disk is now twice as close as the earlier request. Thus, the head will move forward.
- This tunable controls how long an async (buffered write) request can go unserviced. After the expiration time (in milliseconds), a single starved async request will be moved to the dispatch list. The default is
- This is the same as the fifo_expire_async tunable, for for synchronous (read and O_DIRECT write) requests. The default is
- When set, CFQ will idle on the last process issuing I/O in a cgroup. This should be set to
1when using proportional weight I/O cgroups and setting
0(typically done on fast storage).
- If group isolation is enabled (set to
1), it provides a stronger isolation between groups at the expense of throughput. Generally speaking, if group isolation is disabled, fairness is provided for sequential workloads only. Enabling group isolation provides fairness for both sequential and random workloads. The default value is
0(disabled). Refer to
Documentation/cgroups/blkio-controller.txtfor further information.
- When low latency is enabled (set to
1), CFQ attempts to provide a maximum wait time of 300 ms for each process issuing I/O on a device. This favors fairness over throughput. Disabling low latency (setting it to
0) ignores target latency, allowing each process in the system to get a full time slice. Low latency is enabled by default.
- The quantum controls the number of I/Os that CFQ will send to the storage at a time, essentially limiting the device queue depth. By default, this is set to
8. The storage may support much deeper queue depths, but increasing
quantumwill also have a negative impact on latency, especially in the presence of large sequential write workloads.
- This tunable controls the time slice allotted to each process issuing asynchronous (buffered write) I/O. By default it is set to
- This specifies how long CFQ should idle while waiting for further requests. The default value in Red Hat Enterprise Linux 6.1 and earlier is
8ms. In Red Hat Enterprise Linux 6.2 and later, the default value is
0. The zero value improves the throughput of external RAID storage by removing all idling at the queue and service tree level. However, a zero value can degrade throughput on internal non-RAID storage, because it increases the overall number of seeks. For non-RAID storage, we recommend a
slice_idlevalue that is greater than 0.
- This tunable dictates the time slice allotted to a process issuing synchronous (read or direct write) I/O. The default is
6.4.2. Deadline I/O Scheduler
- This determines the number of reads or writes to issue in a single batch. The default is
16. Setting this to a higher value may result in better throughput, but will also increase latency.
- You can set this tunable to
0if you know your workload will never generate front merges. Unless you have measured the overhead of this check, it is advisable to leave it at its default setting (
- This tunable allows you to set the number of milliseconds in which a read request should be serviced. By default, this is set to
500ms (half a second).
- This tunable allows you to set the number of milliseconds in which a write request should be serviced. By default, this is set to
5000ms (five seconds).
- This tunable controls how many read batches can be processed before processing a single write batch. The higher this is set, the more preference is given to reads.
- In some cases, the overhead of I/O events contributing to the entropy pool for
/dev/randomis measurable. In such cases, it may be desirable to set this value to 0.
- By default, the maximum request size sent to disk is
512KB. This tunable can be used to either raise or lower that value. The minimum value is limited by the logical block size; the maximum value is limited by
max_hw_sectors_kb. There are some SSDs which perform worse when I/O sizes exceed the internal erase block size. In such cases, it is recommended to tune
max_hw_sectors_kbdown to the erase block size. You can test for this using an I/O generator such as iozone or aio-stress, varying the record size from, for example,
- This tunable is primarily a debugging aid. Most workloads benefit from request merging (even on faster storage such as SSDs). In some cases, however, it is desirable to disable merging, such as when you want to see how many IOPS a storage back-end can process without disabling read-ahead or performing random I/O.
- Each request queue has a limit on the total number of request descriptors that can be allocated for each of read and write I/Os. By default, the number is
128, meaning 128 reads and 128 writes can be queued at a time before putting a process to sleep. The process put to sleep is the next to try to allocate a request, not necessarily the process that has allocated all of the available requests.If you have a latency-sensitive application, then you should consider lowering the value of
nr_requestsin your request queue and limiting the command queue depth on the storage to a low number (even as low as
1), so that writeback I/O cannot allocate all of the available request descriptors and fill up the device queue with write I/O. Once
nr_requestshave been allocated, all other processes attempting to perform I/O will be put to sleep to wait for requests to become available. This makes things more fair, as the requests are then distributed in a round-robin fashion (instead of letting one process consume them all in rapid succession). Note that this is only a problem when using the deadline or noop schedulers, as the default CFQ configuration protects against this situation.
- In some circumstances, the underlying storage will report an optimal I/O size. This is most common in hardware and software RAID, where the optimal I/O size is the stripe size. If this value is reported, applications should issue I/O aligned to and in multiples of the optimal I/O size whenever possible.
- The operating system can detect when an application is reading data sequentially from a file or from disk. In such cases, it performs an intelligent read-ahead algorithm, whereby more data than is requested by the user is read from disk. Thus, when the user next attempts to read a block of data, it will already by in the operating system's page cache. The potential down side to this is that the operating system can read more data from disk than necessary, which occupies space in the page cache until it is evicted because of high memory pressure. Having multiple processes doing false read-ahead would increase memory pressure in this circumstance.For device mapper devices, it is often a good idea to increase the value of
read_ahead_kbto a large number, such as
8192. The reason is that a device mapper device is often made up of multiple underlying devices. Setting this value to the default (
128KB) multiplied by the number of devices you are mapping is a good starting point for tuning.
- Traditional hard disks have been rotational (made up of spinning platters). SSDs, however, are not. Most SSDs will advertise this properly. If, however, you come across a device that does not advertise this flag properly, it may be necessary to set rotational to
0manually; when rotational is disabled, the I/O elevator does not use logic that is meant to reduce seeks, since there is little penalty for seek operations on non-rotational media.
- I/O completions can be processed on a different CPU from the one that issued the I/O. Setting
1causes the kernel to deliver completions to the CPU on which the I/O was issued. This can improve CPU data caching effectiveness.
Chapter 7. File Systems
7.1. Tuning Considerations for File Systems
7.1.1. Formatting Options
Block size can be selected at
mkfs time. The range of valid sizes depends on the system: the upper limit is the maximum page size of the host system, while the lower limit depends on the file system used. The default block size is appropriate for most use cases.
If your system uses striped storage such as RAID5, you can improve performance by aligning data and metadata with the underlying storage geometry at
mkfs time. For software RAID (LVM or MD) and some enterprise hardware storage, this information is queried and set automatically, but in many cases the administrator must specify this geometry manually with
mkfs at the command line.
Metadata-intensive workloads mean that the log section of a journaling file system (such as ext4 and XFS) is updated extremely frequently. To minimize seek time from file system to journal, you can place the journal on dedicated storage. Note, however, that placing the journal on external storage that is slower than the primary file system can nullify any potential advantage associated with using external storage.
mkfstime, with journal devices being specified at mount time. Refer to the
mount(8)man pages for further information.
7.1.2. Mount Options
A write barrier is a kernel mechanism used to ensure that file system metadata is correctly written and ordered on persistent storage, even when storage devices with volatile write caches lose power. File systems with write barriers enabled also ensure that any data transmitted via
fsync() persists across a power outage. Red Hat Enterprise Linux enables barriers by default on all hardware that supports them.
fsync()heavily, or create and delete many small files. For storage with no volatile write cache, or in the rare case where file system inconsistencies and data loss after a power loss is acceptable, barriers can be disabled by using the
nobarriermount option. For further information, refer to the Storage Administration Guide.
Historically, when a file is read, the access time (
atime) for that file must be updated in the inode metadata, which involves additional write I/O. If accurate
atime metadata is not required, mount the file system with the
noatime option to eliminate these metadata updates. In most cases, however,
atime is not a large overhead due to the default relative atime (or
relatime) behavior in the Red Hat Enterprise Linux 6 kernel. The
relatime behavior only updates
atime if the previous
atime is older than the modification time (
mtime) or status change time (
noatimeoption also enables
nodiratimebehavior; there is no need to set both
Read-ahead speeds up file access by pre-fetching data and loading it into the page cache so that it can be available earlier in memory instead of from disk. Some workloads, such as those involving heavy streaming of sequential I/O, benefit from high read-ahead values.
blockdevcommand to view and edit the read-ahead value. To view the current read-ahead value for a particular block device, run:
# blockdev -getra device
# blockdev -setra N device
blockdevcommand will not persist between boots. We recommend creating a run level
init.dscript to set this value during boot.
7.1.3. File system maintenance
Batch discard and online discard operations are features of mounted file systems that discard blocks which are not in use by the file system. These operations are useful for both solid-state drives and thinly-provisioned storage.
fstrimcommand. This command discards all unused blocks in a file system that match the user's criteria. Both operation types are supported for use with the XFS and ext4 file systems in Red Hat Enterprise Linux 6.2 and later as long as the block device underlying the file system supports physical discard operations. Physical discard operations are supported if the value of
/sys/block/device/queue/discard_max_bytesis not zero.
-o discardoption (either in
/etc/fstabor as part of the
mountcommand), and run in realtime without user intervention. Online discard operations only discard blocks that are transitioning from used to free. Online discard operations are supported on ext4 file systems in Red Hat Enterprise Linux 6.2 and later, and on XFS file systems in Red Hat Enterprise Linux 6.4 and later.
7.1.4. Application Considerations
The ext4, XFS, and GFS2 file systems support efficient space pre-allocation via the
fallocate(2) glibc call. In cases where files may otherwise become badly fragmented due to write patterns, leading to poor read performance, space preallocation can be a useful technique. Pre-allocation marks disk space as if it has been allocated to a file, without writing any data into that space. Until real data is written to a pre-allocated block, read operations will return zeroes.
7.2. Profiles for file system performance
- A server profile for typical latency performance tuning. It disables tuned and ktune power-saving mechanisms. The
cpuspeedmode changes to
performance. The I/O elevator is changed to
deadlinefor each device. The
cpu_dma_latencyparameter is registered with a value of
1(the lowest possible latency) for power management quality-of-service to limit latency where possible.
- A server profile for typical throughput performance tuning. This profile is recommended if the system does not have enterprise-class storage. It is the same as
kernel.sched_min_granularity_ns(scheduler minimal preemption granularity) is set to
kernel.sched_wakeup_granularity_ns(scheduler wake-up granularity) is set to
vm.dirty_ratio(virtual memory dirty ratio) is set to 40%, and
- transparent huge pages are enabled.
- This profile is recommended for enterprise-sized server configurations with enterprise-class storage, including battery-backed controller cache protection and management of on-disk cache. It is the same as the
readaheadvalue is set to
- non root/boot file systems are re-mounted with
man tuned-adm), or in the Power Management Guide available from http://access.redhat.com/site/documentation/Red_Hat_Enterprise_Linux/.
7.3. File Systems
7.3.1. The Ext4 File System
- Inode table initialization
- For very large file systems, the
mkfs.ext4process can take a very long time to initialize all inode tables in the file system. This process can be deferred with the
-E lazy_itable_init=1option. If this is used, kernel processes will continue to initialize the file system after it is mounted. The rate at which this initialization occurs can be controlled with the
-o init_itable=noption for the
mountcommand, where the amount of time spent performing this background initialization is roughly 1/n. The default value for
- Auto-fsync behavior
- Because some applications do not always properly
fsync()after renaming an existing file, or truncating and rewriting, ext4 defaults to automatic syncing of files after replace-via-rename and replace-via-truncate operations. This behavior is largely consistent with older ext3 filesystem behavior. However,
fsync()operations can be time consuming, so if this automatic behavior is not required, use the
-o noauto_da_allocoption with the
mountcommand to disable it. This will mean that the application must explicitly use
fsync()to ensure data persistence.
- Journal I/O priority
- By default, journal commit I/O is given a slightly higher priority than normal I/O. This priority can be controlled with the
journal_ioprio=noption of the
mountcommand. The default value is
3. Valid values range from 0 to 7, with 0 being the highest priority I/O.
mkfsand tuning options, please see the
mount(8)man pages, as well as the
Documentation/filesystems/ext4.txtfile in the kernel-doc package.
7.3.2. The XFS File System
mkfstime vary the width of the b-trees, which changes the scalability characteristics of different subsystems.
220.127.116.11. Basic tuning for XFS
mkfs.xfscommand automatically configures itself with the correct stripe unit and width to align with the hardware. This may need to be manually configured if hardware RAID is in use.
inode64mount option is highly recommended for multi-terabyte file systems, except where the file system is exported via NFS and legacy 32-bit NFS clients require access to the file system.
logbsizemount option is recommended for file systems that are modified frequently, or in bursts. The default value is
MAX(32 KB, log stripe unit), and the maximum size is 256 KB. A value of 256 KB is recommended for file systems that undergo heavy modifications.
18.104.22.168. Advanced tuning for XFS
22.214.171.124.1. Optimizing for a large number of files
mkfs.xfscommand. If you encounter the file limit after file system creation (usually indicated by ENOSPC errors when attempting to create a file or directory even though free space is available), you can adjust the limit with the
126.96.36.199.2. Optimizing for a large number of files in a single directory
mkfs. The minimum directory block is the file system block size, which defaults to
MAX(4 KB, file system block size). In general, there is no reason to reduce the directory block size.
- file systems requiring no more than 1–2 million directory entries (with entry name lengths of 20–40 bytes) perform best with the default configuration of 4 KB file system block size and 4 KB directory block size.
- file systems requiring between 1–10 million directory entries perform better with a larger block size of 16 KB
- file systems requiring more than 10 million directory entries perform better with an even larger block size of 64 KB
188.8.131.52.3. Optimising for concurrency
184.108.40.206.4. Optimising for applications that use extended attributes
220.127.116.11.5. Optimising for sustained metadata modifications
mkfsdoes this by default for MD and DM devices, but for hardware RAID it may need to be specified. Setting this correctly avoids all possibility of log I/O causing unaligned I/O and subsequent read-modify-write operations when writing modifications to disk.
logbsize) increases the speed at which changes can be written to the log. The default log buffer size is
MAX(32 KB, log stripe unit), and the maximum size is 256 KB. In general, a larger value results in faster performance. However, under fsync-heavy workloads, small log buffers can be noticeably faster than large buffers with a large stripe unit alignment.
delaylogmount option also improves sustained metadata modification performance by reducing the number of changes to the log. It achieves this by aggregating individual changes in memory before writing them to the log: frequently modified metadata is written to the log periodically instead of on every modification. This option increases the memory usage of tracking dirty metadata and increases the potential lost operations when a crash occurs, but can improve metadata modification speed and scalability by an order of magnitude or more. Use of this option does not reduce data or metadata integrity when
syncare used to ensure data and metadata is written to disk.
Read and Write Size
- Use the
rsize=value_in_bytesoption to set the network read size. The recommended size is 1 MiB for servers that support the POSIX extension, for example Samba, and 60 KiB for Windows servers.
- Use the
wsize=value_in_bytesoption to set the default network write size. The recommended size is 1 MiB for servers that support the POSIX extension, for example Samba, and 65 KiB for Windows servers.
CIFS Installation Considerations
vm.dirty_background_bytes=536870912 vm.dirty_bytes=1073741824 vm.dirty_expire_centisecs=250 vm.dirty_writeback_centisecs=500
cache=none– disables caching. Applications have to wait while data is being sent.
cache=loose– enables caching while increasing the danger of data corruption.
cache=strict– adheres strictly to the protocol requirements where caching is regulated by the server. You can set the
cache=strictoption in Red Hat Enterprise Linux 6.6 and later.
cache=looseoption is set by default in Red Hat Enterprise Linux 6. Using
cache=strictis recommended, as
cache=stricthelps to reduce data corruption, although performance is slightly impacted.
7.5.1. Global File System 2
Tattribute, like so.
chattr +T directory
- Pre-allocate files and directories with
fallocatewhere possible, to optimize the allocation process and avoid the need to lock source pages.
- Minimize the areas of the file system that are shared between multiple nodes to minimize cross-node cache invalidation and improve performance. For example, if multiple nodes mount the same file system, but access different sub-directories, you will likely achieve better performance by moving one subdirectory to a separate file system.
- Select an optimal resource group size and number. This depends on typical file sizes and available free space on the system, and affects the likelihood that multiple nodes will attempt to use a resource group simultaneously. Too many resource groups can slow block allocation while allocation space is located, while too few resource groups can cause lock contention during deallocation. It is generally best to test multiple configurations to determine which is best for your workload.
- Select your storage hardware according to the expected I/O patterns from cluster nodes and the performance requirements of the file system.
- Use solid-state storage where possible to lower seek time.
- Create an appropriately-sized file system for your workload, and ensure that the file system is never at more than 80% capacity. Smaller file systems will have proportionally shorter backup times, and require less time and memory for file system checks, but are subject to high fragmentation if they are too small for their workload.
- Set larger journal sizes for metadata-intensive workloads, or when journaled data is in use. Although this uses more memory, it improves performance because more journaling space is available to store data before a write is necessary.
- Ensure that clocks on GFS2 nodes are synchronized to avoid issues with networked applications. We recommend using NTP (Network Time Protocol).
- Unless file or directory access times are critical to the operation of your application, mount the file system with the
NoteRed Hat strongly recommends the use of the
noatimeoption with GFS2.
- If you need to use quotas, try to reduce the frequency of quota synchronization transactions or use fuzzy quota synchronization to prevent performance issues arising from constant quota file updates.
NoteFuzzy quota accounting can allow users and groups to slightly exceed their quota limit. To minimize this issue, GFS2 dynamically reduces the synchronization period as a user or group approaches its quota limit.
Chapter 8. Networking
8.1. Network Performance Enhancements
Receive Packet Steering (RPS)
rxqueue to have its receive
softirqworkload distributed among several CPUs. This helps prevent network traffic from being bottlenecked on a single NIC hardware queue.
ethXwith the NIC's corresponding device name (for example,
rx-Nwith the specified NIC receive queue. This will allow the specified CPUs in the file to process data from queue
ethX. When specifying CPUs, consider the queue's cache affinity .
Receive Flow Steering
- This controls the maximum number of sockets/flows that the kernel can steer towards any specified CPU. This is a system-wide, shared limit.
- This controls the maximum number of sockets/flows that the kernel can steer for a specified receive queue (
rx-N) on a NIC (
ethX). Note that sum of all per-queue values for this tunable on all NICs should be equal or less than that of
getsockopt support for TCP thin-streams
getsockoptcall has been enhanced to support two extra options:
- This Boolean enables dynamic triggering of retransmissions after one dupACK for thin streams.
- This Boolean enables dynamic triggering of linear timeouts for thin streams.
file:///usr/share/doc/kernel-doc-version/Documentation/networking/ip-sysctl.txt. For more information about thin-streams, refer to
Transparent Proxy (TProxy) support
8.2. Optimized Network Settings
- A command-line utility that prints network connections, routing tables, interface statistics, masquerade connections and multicast memberships. It retrieves information about the networking subsystem from the
/proc/net/file system. These files include:
For more information about
/proc/net/tcp(TCP socket information)
/proc/net/unix(Unix domain socket information)
netstatand its referenced files from
/proc/net/, refer to the
- A monitoring utility that monitors packets dropped by the kernel. For more information, refer to the
- A utility for managing and monitoring routes, devices, policy routing, and tunnels. For more information, refer to the
- A utility for displaying and changing NIC settings. For more information, refer to the
- A file that displays ASCII data needed for the IP, ICMP, TCP, and UDP management information bases for an
snmpagent. It also displays real-time UDP-lite statistics.
/proc/net/snmpindicates that one or more socket receive queues are full when the network stack attempts to queue new frames into an application's socket.
Socket receive buffer size
sk_stream_wait_memory.stp, suggests that the socket queue's drain rate is too slow, then you can increase the depth of the application's socket queue. To do so, increase the size of receive buffers used by sockets by configuring either of the following values:
- A kernel parameter that controls the default size of receive buffers used by sockets. To configure this, run the following command:
sysctl -w net.core.rmem_default=NReplace
Nwith the desired buffer size, in bytes. To determine the value for this kernel parameter, view
/proc/sys/net/core/rmem_default. Bear in mind that the value of
rmem_defaultshould be no greater than
/proc/sys/net/core/rmem_max); if need be, increase the value of
- A socket option that controls the maximum size of a socket's receive buffer, in bytes. For more information on
SO_RCVBUF, refer to the man page for more details:
man 7 socket.To configure
SO_RCVBUF, use the
setsockoptutility. You can retrieve the current
getsockopt. For more information using both utilities, refer to the
8.3. Overview of Packet Reception
Figure 8.1. Network receive path diagram
- Hardware Reception: the network interface card (NIC) receives the frame on the wire. Depending on its driver configuration, the NIC transfers the frame either to an internal hardware buffer memory or to a specified ring buffer.
- Hard IRQ: the NIC asserts the presence of a net frame by interrupting the CPU. This causes the NIC driver to acknowledge the interrupt and schedule the soft IRQ operation.
- Soft IRQ: this stage implements the actual frame-receiving process, and is run in
softirqcontext. This means that the stage pre-empts all applications running on the specified CPU, but still allows hard IRQs to be asserted.In this context (running on the same CPU as hard IRQ, thereby minimizing locking overhead), the kernel actually removes the frame from the NIC hardware buffers and processes it through the network stack. From there, the frame is either forwarded, discarded, or passed to a target listening socket.When passed to a socket, the frame is appended to the application that owns the socket. This process is done iteratively until the NIC hardware buffer runs out of frames, or until the device weight (
dev_weight). For more information about device weight, refer to Section 8.4.1, “NIC Hardware Buffer”
- Application receive: the application receives the frame and dequeues it from any owned sockets via the standard POSIX calls (
recvfrom). At this point, data received over the network no longer exists on the network stack.
numadNUMA daemon, CPU power states, interrupt balancing, pause frames, interrupt coalescence, adapter queue (
netdevbacklog), adapter RX and TX buffers, adapter TX queue, module parameters, adapter offloading, Jumbo Frames, TCP and UDP protocol tuning, and NUMA locality.
8.4. Resolving Common Queuing/Frame Loss Issues
8.4.1. NIC Hardware Buffer
softirq, which the NIC asserts via an interrupt. To interrogate the status of this queue, use the following command:
ethtool -S ethX
ethXwith the NIC's corresponding device name. This will display how many frames have been dropped within
ethX. Often, a drop occurs because the queue runs out of buffer space in which to store frames.
- Input traffic
- You can help prevent queue overruns by slowing down input traffic. This can be achieved by filtering, reducing the number of joined multicast groups, lowering broadcast traffic, and the like.
- Queue length
- Alternatively, you can also increase the queue length. This involves increasing the number of buffers in a specified queue to whatever maximum the driver will allow. To do so, edit the
txring parameters of
ethtool --set-ring ethXAppend the appropriate
txvalues to the aforementioned command. For more information, refer to
- Device weight
- You can also increase the rate at which a queue is drained. To do this, adjust the NIC's device weight accordingly. This attribute refers to the maximum number of frames that the NIC can receive before the
softirqcontext has to yield the CPU and reschedule itself. It is controlled by the
8.4.2. Socket Queue
softirqcontext. Applications then drain the queues of their corresponding sockets via calls to
recvfrom, and the like.
Recv-Qcolumn displays the queue size. Generally speaking, overruns in the socket queue are managed in the same way as NIC hardware buffer overruns (i.e. Section 8.4.1, “NIC Hardware Buffer”):
- Input traffic
- The first option is to slow down input traffic by configuring the rate at which the queue fills. To do so, either filter frames or pre-emptively drop them. You can also slow down input traffic by lowering the NIC's device weight.
- Queue depth
- You can also avoid socket queue overruns by increasing the queue depth. To do so, increase the value of either the
rmem_defaultkernel parameter or the
SO_RCVBUFsocket option. For more information on both, refer to Section 8.2, “Optimized Network Settings”.
- Application call frequency
- Whenever possible, optimize the application to perform calls more frequently. This involves modifying or reconfiguring the network application to perform more frequent POSIX calls (such as
read). In turn, this allows an application to drain the queue faster.
8.5. Multicast Considerations
softirqcontext's execution time. Adding a listener to a multicast group implies that the kernel must create an additional copy for each frame received for that group.
softirqcontext can lead to frame drops at both the network card and the socket queue. Increased
softirqruntimes translate to reduced opportunity for applications to run on heavily-loaded systems, so the rate at which multicast frames are lost increases as the number of applications listening to a high-volume multicast group increases.
8.6. Receive-Side Scaling (RSS)
/proc/interrupts. For example, if you are interested in the
# egrep 'CPU|p1p1' /proc/interrupts CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 89: 40187 0 0 0 0 0 IR-PCI-MSI-edge p1p1-0 90: 0 790 0 0 0 0 IR-PCI-MSI-edge p1p1-1 91: 0 0 959 0 0 0 IR-PCI-MSI-edge p1p1-2 92: 0 0 0 3310 0 0 IR-PCI-MSI-edge p1p1-3 93: 0 0 0 0 622 0 IR-PCI-MSI-edge p1p1-4 94: 0 0 0 0 0 2475 IR-PCI-MSI-edge p1p1-5
p1p1-5). It also shows how many interrupts were processed by each queue, and which CPU serviced the interrupt. In this case, there are 6 queues because by default, this particular NIC driver creates one queue per CPU, and this system has 6 CPUs. This is a fairly common pattern amongst NIC drivers.
ls -1 /sys/devices/*/*/device_pci_address/msi_irqsafter the network driver is loaded. For example, if you are interested in a device with a PCI address of
0000:01:00.0, you can list the interrupt request queues of that device with the following command:
# ls -1 /sys/devices/*/*/0000:01:00.0/msi_irqs 101 102 103 104 105 106 107 108 109
bnx2xdriver, it is configured in
num_queues. For the
sfcdriver, it is configured in the
rss_cpusparameter. Regardless, it is typically configured in
/sys/class/net/device/queues/rx-queue/, where device is the name of the network device (such as
eth1) and rx-queue is the name of the appropriate receive queue.
--set-rxfh-indirparameters to modify how network activity is distributed, and weight certain types of network activity as more important than others.
irqbalancedaemon can be used in conjunction with RSS to reduce the likelihood of cross-node memory transfers and cache line bouncing. This lowers the latency of processing network packets. If both
irqbalanceand RSS are in use, lowest latency is achieved by ensuring that
irqbalancedirects interrupts associated with a network device to the appropriate RSS queue.
8.7. Receive Packet Steering (RPS)
- RPS can be used with any network interface card.
- It is easy to add software filters to RPS to deal with new protocols.
- RPS does not increase the hardware interrupt rate of the network device. However, it does introduce inter-processor interrupts.
/sys/class/net/device/queues/rx-queue/rps_cpusfile, where device is the name of the network device (such as
eth0) and rx-queue is the name of the appropriate receive queue (such as
rps_cpusfile is zero. This disables RPS, so the CPU that handles the network interrupt also processes the packet.
rps_cpusfile with the CPUs that should process packets from the specified network device and receive queue.
rps_cpusfiles use comma-delimited CPU bitmaps. Therefore, to allow a CPU to handle interrupts for the receive queue on an interface, set the value of their positions in the bitmap to 1. For example, to handle interrupts with CPUs 0, 1, 2, and 3, set the value of
f(the hexadecimal value for 15).
8.8. Receive Flow Steering (RFS)
- Set the value of this file to the maximum expected number of concurrently active connections. We recommend a value of
32768for moderate server loads. All values entered are rounded up to the nearest power of 2 in practice.
- Replace device with the name of the network device you wish to configure (for example,
eth0), and rx-queue with the receive queue you wish to configure (for example,
rx-0).Set the value of this file to the value of
Nis the number of receive queues on a device. For example, if
rps_flow_entriesis set to
32768and there are 16 configured receive queues,
rps_flow_cntshould be set to
2048. For single-queue devices, the value of
rps_flow_cntis the same as the value of
tasksetin conjunction with RFS to pin applications to specific cores, sockets, or NUMA nodes. This can help prevent packets from being processed out of order.
8.9. Accelerated RFS
- Accelerated RFS must be supported by the network interface card. Accelerated RFS is supported by cards that export the
ntuplefiltering must be enabled.
8.10. NIC Offloads
- TCP Segmentation Offload (TSO)
- Uses the TCP protocol to send large packets. Uses the NIC to handle segmentation, and then adds the TCP, IP and data link layer protocol headers to each segment.
- UDP Fragmentation Offload (UFO)
- Uses the UDP protocol to send large packets. Uses the NIC to handle IP fragmentation into MTU sized packets for large UDP datagrams.
- Generic Segmentation Offload (GSO)
- Uses the TCP or UDP protocol to send large packets. If the NIC cannot handle segmentation/fragmentation, GSO performs the same operations, bypassing the NIC hardware. This is achieved by delaying segmentation until as late as possible, for example, when the packet is processed by the device driver.
- Large Receive Offload (LRO)
- Uses the TCP protocol. All incoming packets are re-segmented as they are received, reducing the number of segments the system has to process. They can be merged either in the driver or using the NIC. A problem with LRO is that it tends to resegment all incoming packets, often ignoring differences in headers and other information which can cause errors. It is generally not possible to use LRO when IP forwarding is enabled. LRO in combination with IP forwarding can lead to checksum errors. Forwarding is enabled if
/proc/sys/net/ipv4/ip_forwardis set to 1.
- Generic Receive Offload (GRO)
- Uses either the TCP or UDP protocols. GRO is more rigorous than LRO when resegmenting packets. For example it checks the MAC headers of each packet, which must match, only a limited number of TCP or IP headers can be different, and the TCP timestamps must match. Resegmenting can be handled by either the NIC or the GSO code.
8.10.1. Using NIC Offloads
ethtoolcommand. Some device settings may be listed as
fixed, meaning they cannot be changed.
Example 8.1. Check Current Offload Settings
$ ethtool -k em1
Features for em1: rx-checksumming: on tx-checksumming: on tx-checksum-ipv4: off [fixed] tx-checksum-ip-generic: on tx-checksum-ipv6: off [fixed] tx-checksum-fcoe-crc: off [fixed] tx-checksum-sctp: off [fixed] scatter-gather: on tx-scatter-gather: on tx-scatter-gather-fraglist: off [fixed] tcp-segmentation-offload: on tx-tcp-segmentation: on tx-tcp-ecn-segmentation: off [fixed] tx-tcp6-segmentation: on udp-fragmentation-offload: off [fixed] generic-segmentation-offload: on generic-receive-offload: on large-receive-offload: off [fixed] rx-vlan-offload: on tx-vlan-offload: on ntuple-filters: off [fixed] receive-hashing: on highdma: on [fixed] rx-vlan-filter: off [fixed] vlan-challenged: off [fixed] tx-lockless: off [fixed] netns-local: off [fixed] tx-gso-robust: off [fixed] tx-fcoe-segmentation: off [fixed] tx-gre-segmentation: off [fixed] tx-ipip-segmentation: off [fixed] tx-sit-segmentation: off [fixed] tx-udp_tnl-segmentation: off [fixed] tx-mpls-segmentation: off [fixed] fcoe-mtu: off [fixed] tx-nocache-copy: off loopback: off [fixed] rx-fcs: off rx-all: off tx-vlan-stag-hw-insert: off [fixed] rx-vlan-stag-hw-parse: off [fixed] rx-vlan-stag-filter: off [fixed] l2-fwd-offload: off [fixed] busy-poll: off [fixed]
Appendix A. Revision History
|Revision 4.6-1||Tue Jul 17 2018|
|Revision 4.6-0||Thu Aug 10 2017|
|Revision 4.2-0||Tue May 10 2016|
|Revision 4.1-0||Tue May 06 2014|
|Revision 4.0-43||Wed Nov 13 2013|
|Revision 4.0-6||Thu Oct 4 2012|
|Revision 1.0-0||Friday December 02 2011|