Power, performance and memory
LuxOS puts speed and low resource use first. This page lists the system defaults (package
luxos-tweaks and parts of luxos-desktop/luxos-drivers) and the two user-facing savers:
Data Saver and Battery Saver.
Data Saver (luxos-datasaver)
Toggle: Control Center › Data Saver tile, or the command:
luxos-datasaver on|off|toggle|status
What it does:
- State file
~/.config/luxos/datasaver(exists = on). - Marks every active NetworkManager connection as metered (
nmcli device modify <dev> connection.metered yes), so apps that honour metered connections limit background downloads. - Networks connected later are marked too:
luxos-hubwatches NetworkManager and runsluxos-datasaver reapply;luxos-sessionalso reapplies it at login. - LuxOS Care does not update automatically on a metered connection (reason shown: "The connection is metered (Data Saver)").
- LuxOS Store shows "Data Saver is on - updates are not checked automatically."
luxstill downloads when you run it yourself (passes--datasaverto the backend, which only reminds you of the download size before asking).- System background downloads
reflector.service(mirror list/etc/lux/mirrorlist, converted by theluxos-tweaksdrop-in) andarchlinux-keyring-wkd-sync.serviceare skipped on any metered connection (Data Saver, or a phone hotspot NetworkManager guesses as metered): drop-inExecCondition=/usr/lib/luxos/luxos-unmetered(packageluxos-tweaks). They run again at the next timer elapse on an unmetered connection. - Not changed (not controllable reversibly): Firefox prefs, third-party sync clients.
Turning it off sets connection.metered no on active devices.
Battery Saver (luxos-powersaver)
Toggle: Control Center › Battery Saver, Battery & Power app, or:
luxos-powersaver on|off|toggle|status
- State file
~/.config/luxos/powersaver; original values in~/.config/luxos/powersaver.saved. - On (like macOS Low Power Mode), session part:
- power-profiles-daemon profile power-saver (EPP "power", platform_profile low-power);
- only when
~/.config/luxos/powersaver-60hzexists (Battery & Power, off by default - the mode change blanks the screen for a moment): built-in display (eDP/LVDS/DSI) above 60 Hz is switched to ~60 Hz (also after monitor changes); - backlight dimmed by 20 % (not below 40 %, only when above 40 %);
- GTK animations and Dock magnification stay on (spinners would stop; no real saving). Older versions turned them off; the original value is restored once (update or login).
- System part
luxos-powersaver.service(root, started without a password by polkit rule50-luxos-powersaver.rules, helper/usr/lib/luxos/luxos-powersaver-helper, originals in/run/luxos/powersaver.saved): - CPU turbo/boost off (
intel_pstate/no_turbo,cpufreq/boost, per-policyboost); - HDA audio codec power save 1 s (only if it was 0);
- USB autosuspend for idle devices whose driver handles it (webcam
uvcvideo, Realtek card readers) or that have no driver; input, audio, Bluetooth, network, storage and hubs are left alone; vm.dirty_writeback_centisecs500 → 1500 (fewer disk wake-ups);- pauses
man-db.timer(the Care check keeps running); - marker
/run/luxos/powersaver: LuxOS Care does not update automatically unless charging. - Off: everything restored (previous power profile, refresh rate, brightness if you did not change it meanwhile; the service's stop restores the system values).
- After reboot
/runis empty;luxos-sessionrunsluxos-powersaver reapplyat login. - Deliberately not changed: Wi-Fi power save (already on by default in the kernel), PCIe ASPM
(
powersavecan disable L1 substates and use more power,powersupersaveis unstable on some hardware), SATA link power (already the kernel default on laptops), NMI watchdog (already off), NVIDIA dGPU (runtime PM fromluxos-driversalready powers it off when idle), freezing apps. - Battery Saver sets the Power Saver profile, so games are back on the integrated GPU (see Performance mode below).
Automatic Battery Saver at 20 %
In Battery & Power › Battery Saver the switch Turn on automatically at 20 % creates
~/.config/luxos/powersaver-auto. The top-bar battery indicator (luxos-battery) then turns Battery
Saver on when the battery is discharging at ≤ 20 % (notification "Battery Saver is on – Battery is at
N %. Connect the charger.") and turns it off again when charging – but only if it was turned on
automatically (marker $XDG_RUNTIME_DIR/luxos-powersaver-auto-on).
Stay awake while music or video is playing
Battery & Power › Screen and sleep › Stay awake while music or video is playing (default on; off =
~/.config/luxos/sleep-while-playing exists). xfce4-power-manager handles the lid (it holds logind's
handle-lid-switch inhibitor), so luxos-hub watches MPRIS players over D-Bus (no polling) and
while something plays temporarily sets xfce4-power-manager's lid action to Turn off the screen (if it
was Sleep/Hibernate) and sleep-on-inactivity to Never. The originals are in
~/.config/luxos/sleep-override (restored after 30 s without playback, and at luxos-hub start after a
crash). If the lid was closed while playing, the computer then goes to sleep (via
xfce4-power-manager, which locks the screen). Battery & Power edits the originals while the override
is active.
Battery & Power also offers the power mode (Power Saver / Balanced / Performance, when power-profiles-daemon supports them), screen-off and sleep timeouts, lid action and Advanced Power Settings… (xfce4-power-manager). See Settings apps.
Performance mode: maximum performance including the GPU (luxos-gpu)
Choosing Performance (Battery & Power, or any tool that sets the power-profiles-daemon profile)
switches everything to maximum performance; Balanced and Power Saver switch it back. The only
source of truth is power-profiles-daemon's ActiveProfile: luxos-hub listens for its
PropertiesChanged signal (no polling) and runs luxos-gpu apply on every change and 2 s after login.
apply is idempotent – it compares the wanted state with what is there, so leftovers after a crash,
logout or a changed profile are fixed at the next login.
- CPU: power-profiles-daemon itself (amd-pstate-epp / intel_pstate: EPP
performance; on amd-pstate-epp also theperformancegovernor; platform profile where the firmware has one). Selecting Performance in Battery & Power while Battery Saver is on turns Battery Saver off first (it disables CPU turbo). - Graphics (laptops with hybrid graphics – a discrete NVIDIA or AMD GPU next to the GPU that drives the
screen, detected from sysfs
boot_vga/ueventwithout waking the dGPU): games and demanding apps run on the discrete GPU, the desktop (xfwm4 compositor, panel, Dock) stays on the integrated GPU. - Environment for offload: NVIDIA (proprietary driver)
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia __VK_LAYER_NV_optimus=NVIDIA_only(the same asprime-run); AMD/Intel/nouveau dGPUDRI_PRIME=1. Variables you set yourself are kept. - Native apps:
luxos-apps-sync(package hook) writes a copy of every.desktopfile withCategories=…Game…orPrefersNonDefaultGPU=true(notDBusActivatable) to/var/lib/luxos/apps/applicationswithExec=luxos-gpu run …andX-LuxOS-GPU=true. Launchpad, the menu, Dock, Search and Files use these.luxos-gpu runasks power-profiles-daemon at every launch (a few ms) – in Performance mode it sets the variables, otherwise it just starts the program. - Flatpak apps (Flathub): the Flatpak sandbox does not see the launcher's choice reliably, so
applyadds the variables to your user overrides~/.local/share/flatpak/overrides/<app-id>, group[Environment](same file asflatpak override --user) for game launchers (Steam, Heroic, Lutris, Bottles, Prism Launcher, ATLauncher, itch, RetroArch, RetroDECK, Sober, PCSX2, RPCS3, Cemu, Dolphin, Blender) and every installed Flatpak whose exported.desktopis a game or prefers the discrete GPU. Only missing keys are added; your own keys and values are never changed. What LuxOS added is listed in~/.local/state/luxos/gpu-flatpakand removed when leaving Performance mode (unless you changed the value meanwhile); files LuxOS created are deleted. Steam's own GPU choice ("AMD Radeon Graphics (RADV …)") does not matter then – Vulkan only shows the NVIDIA GPU to games. - NVIDIA PowerMizer "Prefer Maximum Performance" (
nvidia-settings -a [gpu:0]/GpuPowerMizerMode=1in the running X session; the previous value is in$XDG_RUNTIME_DIR/luxos/gpu-powermizerand restored when leaving). Best effort: on PRIME render offload the GPU sleeps (runtime D3) when no app uses it and the driver may return to adaptive clocks after waking up; under game load adaptive mode already runs at full clocks. - Discrete AMD GPU:
power_dpm_force_performance_levelhigh(back to the previous value, usuallyauto) throughluxos-gpu-performance.service(root, started without a password by polkit rule50-luxos-gpu.rules;luxos-gpu system on|off, originals in/run/luxos/gpu-performance.saved). - Battery & Power shows a line under the power modes, e.g. Graphics: NVIDIA GeForce GTX 1650 Mobile / Max-Q for games and demanding apps (Performance) or Graphics: integrated (Performance mode uses … for games).
Limits: a program reads its environment only when it starts – apps and games that are already running
keep their GPU until restarted. If a Flatpak launcher (Steam) is running when the mode changes, a
notification says "Restart Steam to run its games on …" (or that it will use the integrated graphics
again). Flatpak apps on NVIDIA need the matching org.freedesktop.Platform.GL.nvidia-<version> extension
(Flatpak installs it with updates). Dock items pinned from /usr/share/applications directly, programs
started from a terminal and D-Bus-activated apps are not wrapped – use prime-run <app> (NVIDIA) or
luxos-gpu run <app> there. switcheroo-control is deliberately not used: it would put
PrefersNonDefaultGPU apps on the dGPU in every mode (battery), and only GLib launchers honour it.
Commands: luxos-gpu status (detected GPU, profile, offload=yes|no), luxos-gpu env (variables now),
luxos-gpu run <program>, luxos-gpu apply.
Low-memory protection (earlyoom)
LuxOS uses earlyoom (enabled service); systemd-oomd is disabled on upgrade because on Xfce it
would kill the whole session. Drop-in /usr/lib/systemd/system/earlyoom.service.d/10-luxos.conf:
earlyoom -m 4,2 -s 8,4 -r 0 -n --avoid "<protected>" --prefer "<preferred>"
- When free RAM < 4 % and free swap (zram) < 8 %, the process with the highest
oom_scoregetsSIGTERM; below 2 % / 4 % it getsSIGKILL.--avoidsubtracts 300 from the score,--preferadds 300 (names are/proc/PID/comm, at most 15 characters). - Protected (
--avoid): Xorg/Xwayland, lightdm, systemd*, xfce4-session, xfwm4, xfce4-panel and its plugins (wrapper-2.0), xfdesktop, xfsettingsd, plank, luxos-hub, luxos-menubar, luxos-greeter, PipeWire, WirePlumber, NetworkManager, wpa_supplicant, D-Bus, the accessibility bus (at-spi: when it is killed and later restarts, every running GTK app and the top bar crash), polkitd, udisksd, sshd, earlyoom, and the small session services: xfce4-notifyd, xfconfd, xfce4-power-manager, xfce4-screensaver, light-locker, polkit agents, gnome-keyring, dconf-service, xdg-desktop-portal, xdg-document-portal, xdg-permission-store, flatpak-portal/session-helper, gvfs, bamfdaemon, nm-applet, upowerd, bluetoothd. Reason: systemd gives every user serviceoom_score_adj200, so a 3–15 MiB service scored higher than a 4 GB game (adj 0); before 1.0 earlyoom killed dozens of them (notifications 5× in 2 s) without freeing memory. Protected processes can still be killed when they really use the most memory. - Preferred victims (
--prefer): browser tabs/content processes, chromium/chrome, electron, code, node, java, qemu-system-x86, steamwebhelper, WebKitWebProcess. xfce4-notifydrestarts by itself 2 s after it was killed (drop-in/usr/lib/systemd/user/xfce4-notifyd.service.d/10-luxos.conf:Restart=on-abnormal,RestartForceExitStatus=SIGTERM), so notifications come back and D-Bus activation does not hang. The panel volume plugin sends its notifications asynchronously (1.5 s limit), so a stuck notification server can no longer freeze it.luxos-hubshows a critical notification "Memory is running low – “<app>” used too much memory and was closed so the computer would not freeze."
Related cgroup limits:
user-.slice:MemoryHigh=92%– user programs are throttled (pushed to zram) instead of freezing the desktop.lightdm.service:MemoryLow=200M– the display server and login stay responsive.- Fork bombs:
luxos-forkguardandTasksMax8 % per user / 5 % per session, at least min(4096, RAM MB / 2) per session (luxos-tasks-generator), see troubleshooting.md.
zram swap
/etc/systemd/zram-generator.conf (a backup file – local edits are kept):
[zram0]
zram-size = min(ram / 2, 8192)
compression-algorithm = zstd
swap-priority = 100
fs-type = swap
Compressed swap in RAM, half of RAM up to 8 GiB.
/tmp is on disk, not in RAM: Temporary files.
sysctl (/usr/lib/sysctl.d/99-luxos.conf)
| Setting | Value | Why |
|---|---|---|
vm.swappiness |
180 | zram swap is cheap |
vm.page-cluster |
0 | no swap read-ahead for zram |
vm.watermark_boost_factor / vm.watermark_scale_factor |
0 / 10 | smaller reserves |
vm.vfs_cache_pressure |
50 | keep directory/inode caches |
vm.dirty_bytes / vm.dirty_background_bytes |
256 MiB / 64 MiB | fewer stalls when copying big files |
kernel.nmi_watchdog |
0 | fewer interrupts |
net.core.default_qdisc / net.ipv4.tcp_congestion_control |
fq / bbr | faster network (tcp_bbr loaded via modules-load.d) |
net.ipv4.tcp_fastopen |
3 | |
fs.inotify.max_user_watches |
524288 | IDEs, file sync |
luxos-safe adds kernel.yama.ptrace_scope = 2 and fs.suid_dumpable = 0 (see Safe).
I/O schedulers
udev rule 60-luxos-ioschedulers.rules: NVMe → none, SSD/eMMC → mq-deadline, rotating disks → bfq.
CPU scheduler (sched_ext, scx_lavd)
Since LuxOS 1.0 the CPU scheduler on desktops is scx_lavd (package scx-scheds), a
latency-aware sched_ext BPF scheduler: windows, input, audio and
games get the CPU first when the machine is busy. Its default autopilot mode picks powersave,
balanced or performance by load.
/etc/luxos/scheduler.conf(packageluxos-tweaks):SCHEDULER=lavd(default) orSCHEDULER=default(the kernel's own EEVDF scheduler);ARGS=adds options for scx_lavd, e.g.ARGS=--autopowerto follow the power profile (Battery Saver → powersave) instead of the load.- Switch:
luxos-care schedulershows the setting and what runs now;sudo luxos-care scheduler defaultorsudo luxos-care scheduler lavdwrites the file and switches immediately. - In system.lsl the same setting is the key
kernel.scheduler = "lavd" | "default"(written toSCHEDULER=in/etc/luxos/scheduler.conf). luxos-scheduler.servicestarts it after the login screen (After=graphical.target), so loading the BPF program never delays booting.- Safe fallback: without sched_ext in the kernel the unit is skipped; if scx_lavd is missing or the
setting is
defaultit exits quietly. If the scheduler crashes or the kernel ejects it (watchdog), the kernel switches back to EEVDF at once; restart after 10 s with growing delays, after 3 crashes in 24 h the kernel scheduler stays (/run/luxos/scheduler-fallback) until 24 h pass, an update orsudo luxos-care scheduler lavd. An enabledscx_loader.service(packagescx-tools) takes precedence. - Overhead: one mostly idle process (≈ 10 MB binary, typically 10–20 MB RSS) and BPF maps of a few MB;
the scheduling decisions run in the kernel. Disk:
scx-schedsinstalls all upstream schedulers (≈ 160 MB). - Check:
systemctl status luxos-scheduler,cat /sys/kernel/sched_ext/state(enabled),cat /sys/kernel/sched_ext/root/ops(lavd_…).
Boot speed
- Boot menu hidden without waiting: systemd-boot
timeout 0, GRUB (BIOS)GRUB_TIMEOUT=0withGRUB_TIMEOUT_STYLE=hidden. To reach the menu (previous kernel, snapshots, LuxOS Recovery) hold Space (systemd-boot) or hold Shift / press Esc repeatedly (GRUB) while the computer starts. With other systems on the EFI partition the menu stays visible for 3 s. Installs from before 1.0 with GRUB are switched from 1 s to 0 s once by LuxOS Care, only if they still have the LuxOS default (a changedGRUB_TIMEOUTor a visible menu is kept). - A timeout set in the firmware variable (
bootctl set-timeout, or+/-pressed in the systemd-boot menu) overridesloader.conf;bootctl statusshows it,sudo bootctl set-timeout ""removes it. - Boot splash: the progress bar finishes in
luxos-plymouth-finish.serviceright afterbasic.target, in parallel with the network start that LightDM waits for anyway; LightDM then takes the splash picture over without a black gap (plymouth quit --retain-splash,X -background none). - Kernel:
HZ=1000and full preemption (PREEMPT_DYNAMIC, defaultfull;preempt=voluntaryon the kernel command line switches a server to throughput).
journald and shutdown
- Journal limited to
SystemMaxUse=200M,RuntimeMaxUse=64M. DefaultTimeoutStopSec=10sandDefaultTimeoutAbortSec=10sfor system and user managers – faster shutdown/restart.
Kernel, file system, builds
- The kernel is linux-luxos (since LuxOS 0.9.7): vanilla stable Linux from kernel.org (signature
checked), Arch Linux's configuration as the base (every driver as a module – any hardware works
out of the box) plus LuxOS settings (
recipe/config-luxos: BBR TCP congestion control,NR_CPUS=512instead of 8192, transparent huge pages only on request, pinnedHZ=1000, full preemption and sched_ext). No out-of-tree patches. - Built and released automatically by GitHub Actions (https://github.com/luxopes/luxos-kernel): every 6 hours it checks kernel.org, builds the chosen version, boots it in QEMU and loads ~50 typical drivers (storage, USB, graphics, Wi-Fi, Bluetooth, sound) before publishing. Version policy: newest stable series once it has at least 3 point releases (e.g. 7.3.3), until then the newest point release of the current series; never a release candidate, never an older series.
- The LuxOS repository picks a release up only after checking its SHA256SUMS and build provenance
attestation (
scripts/fetch-kernel.sh), then signs it with the LuxOS key. - Headers for DKMS drivers (NVIDIA):
linux-luxos-headers(installed together with the driver). - Older installs used
linux-zen; LuxOS Care switches them automatically (see Care and updates, "Switch to the LuxOS kernel"). - Btrfs with
compress=zstd:1,noatime(subvolumes@,@home,@log,@cache,@tmp) – see Installer. /etc/makepkg.conf.d/luxos.conf:MAKEFLAGS="-j$(nproc)", multithreaded zstd, LTO – faster AUR builds throughlux.
Services enabled by the installer
From /usr/lib/luxos/services: NetworkManager, lightdm, bluetooth, cups.socket, avahi-daemon,
power-profiles-daemon, systemd-timesyncd, earlyoom, fstrim.timer, reflector.timer (writes /etc/lux/mirrorlist; the package cache is cleaned by LuxOS Care, not paccache.timer).
NVIDIA runtime power management
On hybrid-graphics laptops an unused NVIDIA GPU is put to sleep: luxos-drivers ships
options nvidia NVreg_DynamicPowerManagement=0x02 and udev rules setting power/control=auto for the
NVIDIA GPU, its HDMI audio and USB-C controller. See Drivers.