SUSE/saptune

# 1984787 - SUSE LINUX Enterprise Server 12: Installation notes
# Description:    You want to use SAP software on SUSE Linux Enterprise Server 12 (SLES 12) or SUSE Linux Enterprise Server for SAP Applications 12 (SLES for SAP 12).

[version]
VERSION=42
DATE=07.10.2022
DESCRIPTION=SUSE LINUX Enterprise Server 12: Installation notes
REFERENCES=https://launchpad.support.sap.com/#/notes/1984787

[login]
# /etc/systemd/logind.conf.d/saptune-UserTasksMax.conf UserTasksMax setting
# This file configures a parameter of the systemd login manager
# It sets the maximum number of OS tasks each user may run concurrently
# The behaviour of the systemd login manager was changed starting SLES12SP2
# to prevent fork bomb attacks.
# The value for UserTasksMax will be set to 'infinity'
# With this setting your system is vulnerable to fork bomb attacks
#
UserTasksMax=infinity

[service]
# start the related services
uuidd.socket=start
sysstat.service=start

[block]
# The default I/O scheduler for single-queued block layer devices offers
# satisfactory performance for wide range of I/O task, however choosing an
# alternative scheduler may potentially yield better latency characteristics
# and throughput.
# "noop" is an alternative scheduler, in comparison to other schedulers it
# may offer more consistent performance, lower computation overhead, and
# potentially higher throughput.
# For most SAP environments (RAID, storage arrays, virtualizaton) 'noop' is
# the better choice.
# With the new introduced multi-queue scheduler for block layer devices the
# recommended I/O scheduler is 'none' as an equivalent to 'noop' for
# single-queued block layer devices.
#
# So IO_SCHEDULER can now contain a comma separated list of possible
# schedulers, which are checked from left to right. The first one which is
# available in /sys/block/<device>/queue/scheduler will be used as new
# scheduler setting for the respective block device.
#
# When set, all block devices on the system will be switched to one of the
# chosen schedulers.
IO_SCHEDULER=noop, none

[rpm]
# dependencies handled by saptune package installation
systemd 12-SP2 228-142.1
sapinit-systemd-compat 12 1.0-2.1
sapinit-systemd-compat 12-SP1 1.0-2.1
util-linux 12-SP1 2.25-22.1
uuidd 12-SP1 2.25-22
util-linux-systemd 12-SP1 2.25-22.1
psmisc 12-SP5 22.21-6.19.1
kernel-default 12-SP5 4.12.14-122.130

[sysctl]
# vm.dirty_bytes (indirect vm.dirty_ratio)
# Contains the amount of dirty memory at which a process generating disk writes
# will itself start writeback.
# Note: dirty_bytes is the counterpart of dirty_ratio. Only one of them may be
# specified at a time. When one sysctl is written it is immediately taken into
# account to evaluate the dirty memory limits and the other appears as 0 when
# read.
# Note: the minimum value allowed for dirty_bytes is two pages (in bytes); any
# value lower than this limit will be ignored and the old configuration will be
# retained.
#
# vm.dirty_bytes should be set to 629145600 (see TID_7010287)
#
vm.dirty_bytes=629145600

# vm.dirty_background_bytes (indirect vm.dirty_background_ratio)
# Contains the amount of dirty memory at which the background kernel
# flusher threads will start writeback.
# Note: dirty_background_bytes is the counterpart of dirty_background_ratio.
# Only one of them may be specified at a time. When one sysctl is written it is
# immediately taken into account to evaluate the dirty memory limits and the
# other appears as 0 when read.
#
# vm.dirty_background_bytes should be set to 314572800 (see TID_7010287)
#
vm.dirty_background_bytes=314572800