Open topic with navigation
This section describes some Linux operating system settings that you might want to modify to improve IDOL performance and function. You might need additional system privileges to make these changes. In all cases, HPE recommends that you test on your own systems to find the optimal settings for your setup.
For many of the settings listed in this section, values and example commands are given for Red Hat Enterprise Linux (RHEL). You might need to check the default values and suggested commands for other Linux distributions.
The IDOL Content component can use a large number of files for certain tasks, such as indexing, particularly for large indexes. On Linux systems, the number of file descriptors is limited to prevent them from using too much memory. The memory usage of a single file descriptor is low, so it is usually safe to set the limit to a high value. HPE recommends that you increase the limit value to at least
65536 for the user that the IDOL Content component runs as.
You can find an estimate of the number of files that a process (with a specified process ID) is using by using the following command:
ls -l /proc/ProcessID/fd | wc -l
You can find the current limit for the number of files by using the following commands:
Ulimit –Sn Ulimit -Hn
There are two limits to the number of files that processes can use:
ulimitcommands to increase it (up to the hard limit).
To modify the individual process file limit for the user that the IDOL Content component runs as (
UserName), open the
/etc/security/limits.conf configuration file, and add or modify the following lines to modify the soft and hard file limits (where
NewValue is the limit that you want to set, in MB of RAM):
UserName hard nofile NewValue UserName soft nofile NewValue UserName hard nproc NewValue UserName soft nproc NewValue
On Ubuntu, when you use the start-stop-daemon, you might need to run the
ulimit command in the init script to update the hard and soft limits when you start the service.
If you start IDOL component executable files directly (rather than using the init script) by using SSH and
su, you might also need to modify the
/etc/pam.d/su file to uncomment the following line:
# session required pam_limits.so
Transparent Huge pages (THP) is the use of an abstraction layer that automates the creation, management and use of Huge Pages for memory management. In RHEL 6 and later, this feature is turned on by default, but Red Hat does not recommend the use of THP for database workloads. For IDOL, turning this setting off can improve the performance for many query operations.
You can change this setting in a terminal by using the following commands:
echo never > /sys/kernel/mm/redhat_transparent_hugepage/enabled echo never > /sys/kernel/mm/redhat_transparent_hugepage/defrag
On Ubuntu, you can use the following commands:
echo never > /sys/kernel/mm/transparent_hugepage/enabled echo never > /sys/kernel/mm/transparent_hugepage/defrag
You can also turn this setting off at boot time, by adding the following text to the bottom of the
#disable THP at boot time if test -f /sys/kernel/mm/redhat_transparent_hugepage/enabled; then echo never > /sys/kernel/mm/redhat_transparent_hugepage/enabled fi if test -f /sys/kernel/mm/redhat_transparent_hugepage/defrag; then echo never > /sys/kernel/mm/redhat_transparent_hugepage/defrag fi
On Ubuntu, the
/etc/rc.local ends with the line
exit 0, and you must make any changes to the file above that line.
HPE recommends tuning the virtual memory usage for Linux systems for database workloads to improve IDOL performance. In particular, you might want to modify the following settings:
vm.swappiness. This setting controls how much the system favors swapping out runtime memory. The default value on Linux systems is
60, but for database workloads, the recommended value is
10. HPE recommends that you set this value to
10or lower. A value of
1configures the system to only use the minimum amount of swapping, but does not turn it off.
vm.dirty_ratio. This setting controls the maximum percentage of memory that can contain pages that have not yet been written to disk. The default value is
20, but for database workloads the recommended value is
vm.dirty_background_ratio. This setting controls the percentage of memory that can contain pages that have not yet been written to disk before the system starts to write the data in the background. The default is
10, but for database workloads the recommended value is
You can check the current values for these settings by running the following command in the terminal:
# sysctl –a | grep "vm.Parameter"
To change these settings permanently, update the
/etc/sysctl.conf configuration file, to add or modify the following lines:
vm.swappiness = 10 vm.dirty_ratio = 15 vm.dirty_background_ratio = 3
The IDOL Content component can use a large number of memory map areas for certain tasks, such as indexing, particularly for large indexes. On Linux systems, the number of memory mapped areas that a process can use is limited, to a value controlled by the
max_map_count kernel parameter. To prevent IDOL from reaching this limit, HPE recommends that you increase the value of the
max_map_count parameter to the amount of memory on the system in KB /16, but no less than 65536.
This recommendation applies for a single IDOL Server (or Content component) running on the host machine. If you have multiple Content components running on the same host, you might need to limit this value further.
You can find an estimate of the number of memory mapped areas that a process (with a specified process ID) is using by using the following command:
cat /proc/processID/maps | wc -l
You can find the current value of
max_map_count by using the following command:
You can change the value of
max_map_count by using the following command:
The Linux kernel can use several different I/O schedulers to prioritize disk input and output. By default, many Linux distributions use the Completely Fair Queuing (CFQ) scheme for I/O scheduling, which gives input and output requests equal priority. For IDOL systems, HPE recommends that you set I/O scheduling to either
HPE recommends that you always use one of these schedulers, rather than the CFQ scheduler. However, the exact method to use depends on your environment and usage, so you might need to test both of these methods on your system to see which provides the best performance.
You can check whether your disks are SSD or HDD by using the following command:
for i in /sys/block/sd*; do cat $i/queue/rotational; done
This command returns
1 for HDD, and
0 for SSD.
You can find the scheduler for your mounted devices by using the following command:
for i in /sys/block/sd*; do cat $i/queue/scheduler; done
On RHEL 6 and above, for multipath devices, you must also change the
dm-* block device.
This command returns a result of the following type, with the current option surrounded with square brackets:
noop deadline [cfq]
You can change the scheduler by using a command of the following type:
for i in /sys/block/sd*; do echo "noop" > $i/queue/scheduler; done
This example changes the system to use the NOOP scheduler.