Using saptune, you can tune a system for SAP NetWeaver, SAP HANA/SAP BusinessObjects, and SAP S/4HANA applications. This method relies on the system tuning service tuned.
If you used the SAP Installation Wizard to install an SAP application, tuned is usually already active and configured with a profile for the application you installed.
If you did not use the SAP Installation Wizard to install an SAP application, make sure that the packages tuned and saptune are installed on your system.
To tune a system, first find a tuning solutions. To find the appropriate solution, use:
tux > saptune solution list
saptune knows the following tuning solutions (group of SAP notes):
BOBJ Solution for running SAP BusinessObjects.
HANA Solution for running a SAP HANA database.
MAXDB Solution for running a SAP MaxDB database.
NETWEAVER Solution for running SAP NetWeaver application servers.
S4HANA-APPSERVER Solution for running SAP S/4HANA application servers (identical to SAP NetWeaver solution).
S4HANA-APP+DB Solution for running both SAP S/4HANA application servers and SAP HANA on the same host (identical to SAP NetWeaver + SAP HANA solution).
S4HANA-DBSERVER Solution for running the SAP HANA database of an SAP S/4HANA installation (identical to SAP HANA solution)
SAP-ASE Solution for running an SAP Adaptive Server Enterprise database.
Alternatively, you can tune the computer according to recommendations from specific SAP Notes. A list of notes that you can tune for is available via:
root # saptune note list
To set up saptune with a preconfigured solution, use:
root # saptune solution apply SOLUTION
To set up saptune for the recommendations of a specific SAP Note, use:
root # saptune note apply NOTE
NOTE: Combining Optimizations
You can combine solutions and notes. However, you can only have one solution. In rare cases, notes can have conflicting options or parameters. To avoid conflicts, order your notes, keeping in mind that the last note always overrides the conflicting options or parameters in previous notes.
To start saptune and enable it at boot, make sure to run the following command:
root # saptune daemon start
In the background, saptune applies a
tuned profile also named
saptune that is dynamically customized according to
Using tuned-adm list, you can also see this profile.
Every SAP note can be configured freely with:
root # saptune note customise
The command includes changing a value or disabling a parameter.
It is possible to create a new SAP note with:
root # saptune note create
All features of saptune are available.
The shipped configuration of a note can be listed with:
root # saptune note show
The command saptune note|solution verify [note] lists for each active or requested note: the parameter name, the exected value (default), a configured override (done by a saptune customise) the current system value and if the current state is compliant to the SAP recommendation or not.
To show each parameter, use:
root # saptune note|solution simulate
It lists the current system value and the expected values (default and override is listed too).
To disable saptune and to stop and disable tuned run:
root # saptune daemon stop
In addition to or instead of tuning kernel parameters using saptune, you can also use sysctl to make manual adjustments to kernel parameters. However, such changes using sysctl do not persist across reboots by default. To make them persist across reboots, add them to the file /etc/sysctl.conf (or another configuration file read by sysctl).
HINT:If you plan to configure sysctl parameters for your SAP system, consider to use saptune as a central instance for managing your system configuration.
For more information about sysctl, see the man pages sysctl(8), sysctl.conf(5), and sysctl.d(5).
See the following man pages:
man 8 saptune
man 8 saptune_v1
man 8 saptune_v2
man 8 saptune-migrate
man 8 saptune-note
Also see the project home page https://github.com/SUSE/saptune/.