What is lmk fast run?

An Android system running multiple processes in parallel may encounter. Tweak Android Low Memory Killer (LMK) to Your Needs. Improved function of whole RAM Manager (Including fine tuning) - LMK fast run separated from profiles - Adaptive LMK set to enabled on RAM. Disabled LMK fast run for multitasking and balanced profile - Enabled OOM Reaper for supported devices - Fixed crash on app intro for Poco. This one helps keep things running smoothly, and gives us some user.

An Android system running multiple processes in parallel may encounter situations when system memory is exhausted and processes that require more memory experience noticeable delays. Memory pressure, a state in which the system is running short on memory, requires Android to free memory (to alleviate the pressure) by throttling or killing unimportant processes, requesting processes to free noncritical cached resources, and so on.

Historically, Android monitored system memory pressure using an in-kernel low memory killer (LMK) driver, a rigid mechanism that depends on hard-coded values. As of kernel 4.12, the LMK driver is removed from the upstream kernel and the userspace lmkd performs memory monitoring and process killing tasks.

Android 10 and later support a new lmkd mode that uses kernel pressure stall information (PSI) monitors for memory pressure detection. The PSI patchset in the upstream kernel (backported to 4.9 and 4.14 kernels) measures the amount of time that tasks are delayed as a result of memory shortages. As these delays directly affect user experience, they represent a convenient metric for determining memory pressure severity. The upstream kernel also includes PSI monitors that allow privileged userspace processes (such as lmkd) to specify thresholds for these delays and to subscribe to events from the kernel when a threshold is breached.

Because the vmpressure signals (generated by the kernel for memory pressure detection and used by lmkd) often include numerous false positives, lmkd must perform filtering to determine if the memory is under real pressure. This results in unnecessary lmkd wakeups and the use of additional computational resources. Using PSI monitors results in more accurate memory pressure detection and minimizes filtering overhead.

To use PSI monitors instead of vmpressure events, configure the ro.lmk.use_psi property. The default is true, making PSI monitors the default mechanism of memory pressure detection for lmkd. Because PSI monitors require kernel support, the kernel must include the PSI backport patches and be compiled with PSI support enabled (CONFIG_PSI=y).

Android deprecates the LMK driver due to a number of issues, including:

The userspace lmkd implements the same functionality as the in-kernel driver but uses existing kernel mechanisms to detect and estimate memory pressure. Such mechanisms include using kernel-generated vmpressure events or pressure stall information (PSI) monitors to get notifications about memory pressure levels, and using memory cgroup features to limit the memory resources allocated to each process based on process importance.

In Android 9 and later, userspace lmkd activates if an in-kernel LMK driver isn't detected. Because userspace lmkd requires kernel support for memory cgroups, the kernel must be compiled with the following configuration settings:

Userspace lmkd supports kill strategies based on vmpressure events or PSI monitors, their severity, and other hints such as swap utilization. Kill strategies differ between low-memory and high-performance devices:

You can configure the kill strategy using the ro.config.low_ram property. For details, see Low ram configuration.

Userspace lmkd also supports a legacy mode in which it makes kill decisions using the same strategies as the in-kernel LMK driver (that is, free memory and file cache thresholds). To enable legacy mode, set the ro.lmk.use_minfree_levels property to true.

Configure lmkd for a specific device using the following properties.

Example device configuration:

Android 11 improves the lmkd by introducing a new killing strategy. The killing strategy uses a PSI mechanism for memory pressure detection introduced in Android 10. lmkd in Android 11 accounts for memory resource use levels and thrashing to prevent memory starvation and performance degradation. This killing strategy replaces previous strategies and can be used on both high-performance and low-RAM (Android Go) devices.

For Android 11 devices, lmkd requires the following kernel features:

The kernel must be compiled with the following configuration settings:

The memory killing strategy in Android 11 supports the tuning knobs and defaults listed below. These features work on both high-performance and low-RAM devices.

An Android system running multiple processes in parallel may encounter situations when system memory is exhausted and processes that require more memory experience noticeable delays. Memory pressure, a state in which the system is running short on memory, requires Android to free memory (to alleviate the pressure) by throttling or killing unimportant processes, requesting processes to free noncritical cached resources, and so on.

Historically, Android monitored system memory pressure using an in-kernel low memory killer (LMK) driver, a rigid mechanism that depends on hard-coded values. As of kernel 4.12, the LMK driver is removed from the upstream kernel and the userspace lmkd performs memory monitoring and process killing tasks.

Android 10 and later support a new lmkd mode that uses kernel pressure stall information (PSI) monitors for memory pressure detection. The PSI patchset in the upstream kernel (backported to 4.9 and 4.14 kernels) measures the amount of time that tasks are delayed as a result of memory shortages. As these delays directly affect user experience, they represent a convenient metric for determining memory pressure severity. The upstream kernel also includes PSI monitors that allow privileged userspace processes (such as lmkd) to specify thresholds for these delays and to subscribe to events from the kernel when a threshold is breached.

Because the vmpressure signals (generated by the kernel for memory pressure detection and used by lmkd) often include numerous false positives, lmkd must perform filtering to determine if the memory is under real pressure. This results in unnecessary lmkd wakeups and the use of additional computational resources. Using PSI monitors results in more accurate memory pressure detection and minimizes filtering overhead.

To use PSI monitors instead of vmpressure events, configure the ro.lmk.use_psi property. The default is true, making PSI monitors the default mechanism of memory pressure detection for lmkd. Because PSI monitors require kernel support, the kernel must include the PSI backport patches and be compiled with PSI support enabled (CONFIG_PSI=y).

Android deprecates the LMK driver due to a number of issues, including:

The userspace lmkd implements the same functionality as the in-kernel driver but uses existing kernel mechanisms to detect and estimate memory pressure. Such mechanisms include using kernel-generated vmpressure events or pressure stall information (PSI) monitors to get notifications about memory pressure levels, and using memory cgroup features to limit the memory resources allocated to each process based on process importance.

In Android 9 and later, userspace lmkd activates if an in-kernel LMK driver isn't detected. Because userspace lmkd requires kernel support for memory cgroups, the kernel must be compiled with the following configuration settings:

Userspace lmkd supports kill strategies based on vmpressure events or PSI monitors, their severity, and other hints such as swap utilization. Kill strategies differ between low-memory and high-performance devices:

You can configure the kill strategy using the ro.config.low_ram property. For details, see Low ram configuration.

Userspace lmkd also supports a legacy mode in which it makes kill decisions using the same strategies as the in-kernel LMK driver (that is, free memory and file cache thresholds). To enable legacy mode, set the ro.lmk.use_minfree_levels property to true.

Configure lmkd for a specific device using the following properties.

Example device configuration:

Android 11 improves the lmkd by introducing a new killing strategy. The killing strategy uses a PSI mechanism for memory pressure detection introduced in Android 10. lmkd in Android 11 accounts for memory resource use levels and thrashing to prevent memory starvation and performance degradation. This killing strategy replaces previous strategies and can be used on both high-performance and low-RAM (Android Go) devices.

For Android 11 devices, lmkd requires the following kernel features:

The kernel must be compiled with the following configuration settings:

The memory killing strategy in Android 11 supports the tuning knobs and defaults listed below. These features work on both high-performance and low-RAM devices.

The following old tuning knobs also work with the new killing strategy.