LordOS — a free, fast and secure GNU/Linux distribution based on Debian, with its own desktop environment: display server and Wayland compositor in C, a React UI engine on QuickJS, and private native apps.
C cdebiandesktop-environmentebpffirewalllandlocklinuxlinux-distributionopen-sourceprivacyquickjsraspberry-pi-5reactsecuritywaylandwayland-compositor
docs/PAPER.md regenerated from the paper (the final Raspberry Pi 5 run: frame pipeline and GPU drag measured and off by default, the GPU time per frame under load)
Federico Pereira087d143a9451
diff --git a/docs/PAPER.md b/docs/PAPER.mdindex a54c217..f07ab50 100644--- a/docs/PAPER.md+++ b/docs/PAPER.md@@ -614,7 +614,7 @@ All figures below were measured by the project and are documented in the files c- **Software vblank (0.8.5).** A virtual card that completes page flips at once (VMware's `vmwgfx`) made the compositor and its apps draw 500–580 frames a second on a 60 Hz display; LordOS now detects it and paces frames to the refresh on a fixed grid: 59.8 frames a second, p99 18.4 ms, no frame over budget (`results/0.8.5~rc1-beta/vmware-fusion`). On the released 0.8.5-beta, the Test Bench with its 3D view on the same machine measured 59.83 frames a second over 1,796 frames, p99 17.9 ms, one frame over budget, 1,795 presented (`results/0.8.5-beta/vmware-fusion`). The same grid also paces sessions without a monitor, so waiting in whole milliseconds no longer turns 60 frames a second into 57.- **Dragging on the GPU path (0.8.5 fix).** A dragged window is painted from a cached layer; on the GPU path every fully transparent pixel of that layer was taken for a Linux window's hole, and now only pixels inside an app surface are. In 0.8.5-beta small black squares could still show at a dragged window's rounded corners, on the CPU and GPU paths: the layer's corner restore took the saved pixel as opaque. In 0.8.6 (in development) it mixes both pixels alpha included, so the layer stays transparent outside the curve; a test compares each corner with a full repaint on both paths (§10.2).-- **A cheaper drag frame (0.8.6, in development).** A dragged window's frame now paints only the part of its layer that changed and only the changed part of what is below it, with the same pixels: 2,417 recorded frame hashes per path must match, and the one approved change brings rounded corners below the window one level closer to a full repaint. On the GPU path the window itself can be composed by the GPU with the CPU's exact arithmetic, after a self-test of every pixel combination ("GPU drag"), and the next frame can be painted while the previous flip is pending. Results on the Raspberry Pi 5 are in §7.4.+- **A cheaper drag frame (0.8.6, in development).** A dragged window's frame now paints only the part of its layer that changed and only the changed part of what is below it, with the same pixels: 2,417 recorded frame hashes per path must match, and the one approved change brings rounded corners below the window one level closer to a full repaint. On the GPU path the window itself can be composed by the GPU with the CPU's exact arithmetic, after a self-test of every pixel combination ("GPU drag"), and the next frame can be painted while the previous flip is pending; both were measured on the Raspberry Pi 5 and are off by default. Results on the Raspberry Pi 5 are in §7.4.- Dragging a window on one 1280×800 display on the CPU path: about 6.7–6.9 ms of work per frame, around 120 frames per second (VM 118, `docs/DISPLAYS.md`).- The same window on a 2560×1600 display at 150 %: about 5.1 ms per frame.- Video: painting straight from the decoded frame when only an opaque video changed brought `lord-server` from 42 % to 13 % of a core for a windowed 1080p video, and from 92 % to 15 % fullscreen (`docs/ROADMAP.md`, media).@@ -642,11 +642,11 @@ The Raspberry Pi 5 is the only supported board. Results on a real board (16 GB,**Fans.** On the Pi 5 in a test case, `lord-fand` kept the fan off at 50–53 °C during a 4-thread load (the aluminium case acts as a heatsink), drove it to 55 % (4,500 RPM) and full speed (7,400 RPM) with test curves, and restored the kernel's own settings after `SIGTERM` and `kill -9` (`docs/FANS.md`).-**Monitor and image.** Since 0.8.4.1 the Raspberry Pi 5 image shows the desktop on an HDMI monitor at the first boot (the display driver line in `config.txt` now comes after the firmware's auto-detection lines, and LordOS waits up to 30 s for the driver), sets the clock from the network, and ships Chromium and Firefox ESR. Since 0.8.4 the LordOS Pi kernel (`6.18.57-lordos.3-rpi-2712`) also destroys the connections of a blocked app. **Measured on a monitor (LordBench, 0.8.6 in development):** the 0.8.5 image booted with a 1920×1080 60 Hz monitor on either HDMI port reaches the login screen 5.99 s after the kernel starts (systemd: 2.1 s kernel, 4.2 s userspace). With GPU composition (V3D) a window moved by the compositor keeps 59.4 frames per second, with a frame built in 10.9 ms (median) and 13.0 ms (99th percentile) and 1.0 % of frames late; under an all-core load at the lowest priority it falls to 24 frames per second with 96.5 % late, a problem LordBench found: the compositor's cgroup weighed the same as the load's, so the load's low priority did not count. Giving the compositor ten times the CPU weight of an app raised the same test, run without the monitor, from 43–45 to 56–57 frames per second (31–33 % → 7–8 % late) and brought a pointer move to the screen in 22 ms instead of 32 ms (median); with the monitor it was measured only together with the real-time priority below. The compositor's main and paint threads now also run at the lowest real-time priority, which lord-sessiond allows and lord-server drops before it starts anything, so no app inherits it; on VM 116 under load that took late frames from 2.7–2.9 % to 0.28 % and the slowest 1 % of pointer moves from 31–32 to 25 ms, as without load, with the load getting the same CPU time. On the Pi 5 with its monitor the two changes took the loaded test from 24 to 29–30 frames per second and the compositor no longer waits for a CPU, but under the load a frame takes 15–16 ms to build instead of 7, so it misses the 60 Hz refresh; that cause is still being looked for. LordBench's scene had a square meant to turn that stood still, because it was set through a style key the engine lacks; it now turns, which makes the test heavier: with it, that code showed 53–58 frames per second alone and 24–25 under the load. In development for 0.8.6, a dragged window's frame paints only what changed (the changed part of the window's layer and of what is below it), with the same pixels, checked frame by frame against recorded hashes; with that, the same test shows 59.8–60 frames per second alone (99th percentile 11.3–11.6 ms) and 30 under the load, where a frame is built in 12.9 ms (median) instead of about 20. Under the load nearly every frame is still late, because building a frame, the GPU's work and the flip run one after another and miss the 16.7 ms refresh. Composing the dragged window on the GPU stalled in that run (52 frames per second alone), so it was measured off; painting the next frame while the previous one waits for the flip is built and not yet measured on the board. <!-- PI-RESULT: §7.4, the Pi 5 with its monitor and the final build: LordBench Desktop impact alone and under load (fps, late %, build p50) with the defaults (GPU drag where its self-test passes, the frame pipeline while frames are heavy), with LORD_GPU_DRAG=0 and with LORD_PIPELINE=0; replace the GPU drag sentence and "not yet measured on the board" with what was measured, and keep the 53–58 / 24–25 baseline --> In a 3-minute all-core load with the fan the board kept 5.9 GFLOP/s at 55.6 °C at most, and it decodes 1080p video in software at 258 (H.264), 246 (HEVC), 204 (VP9) and 159 (AV1) frames per second.+**Monitor and image.** Since 0.8.4.1 the Raspberry Pi 5 image shows the desktop on an HDMI monitor at the first boot (the display driver line in `config.txt` now comes after the firmware's auto-detection lines, and LordOS waits up to 30 s for the driver), sets the clock from the network, and ships Chromium and Firefox ESR. Since 0.8.4 the LordOS Pi kernel (`6.18.57-lordos.3-rpi-2712`) also destroys the connections of a blocked app. **Measured on a monitor (LordBench, 0.8.6 in development):** the 0.8.5 image booted with a 1920×1080 60 Hz monitor on either HDMI port reaches the login screen 5.99 s after the kernel starts (systemd: 2.1 s kernel, 4.2 s userspace). With GPU composition (V3D) a window moved by the compositor keeps 59.4 frames per second, with a frame built in 10.9 ms (median) and 13.0 ms (99th percentile) and 1.0 % of frames late; under an all-core load at the lowest priority it falls to 24 frames per second with 96.5 % late, a problem LordBench found: the compositor's cgroup weighed the same as the load's, so the load's low priority did not count. Giving the compositor ten times the CPU weight of an app raised the same test, run without the monitor, from 43–45 to 56–57 frames per second (31–33 % → 7–8 % late) and brought a pointer move to the screen in 22 ms instead of 32 ms (median); with the monitor it was measured only together with the real-time priority below. The compositor's main and paint threads now also run at the lowest real-time priority, which lord-sessiond allows and lord-server drops before it starts anything, so no app inherits it; on VM 116 under load that took late frames from 2.7–2.9 % to 0.28 % and the slowest 1 % of pointer moves from 31–32 to 25 ms, as without load, with the load getting the same CPU time. On the Pi 5 with its monitor the two changes took the loaded test from 24 to 29–30 frames per second and the compositor no longer waits for a CPU, but under the load a frame takes 15–16 ms to build instead of 7, so it misses the 60 Hz refresh; that cause is still being looked for. LordBench's scene had a square meant to turn that stood still, because it was set through a style key the engine lacks; it now turns, which makes the test heavier: with it, that code showed 53–58 frames per second alone and 24–25 under the load. In development for 0.8.6, a dragged window's frame paints only what changed (the changed part of the window's layer and of what is below it), with the same pixels, checked frame by frame against recorded hashes; with that, the same test shows 59.8–60 frames per second alone (99th percentile 11.3–11.6 ms) and 30 under the load, where a frame is built in 12.9 ms (median) instead of about 20. Under the load nearly every frame is still late. A final run of the development build (2026-10-29) measured the two remaining changes. Composing the dragged window on the GPU passes its self-test on the Pi's GPU and gave the CPU's exact pixels in all 138 frames compared, but no measurable gain (30.8–31.6 frames per second under the load, against 30.5–31.1 without it). Painting the next frame while the previous one waits for the flip gave 33–36 frames per second under the load, but a pointer move reached the screen 17 ms later alone (42 instead of 25.5 ms, median) and 29 ms later under the load (78 instead of 49 ms). Both stay in the code and are off by default. With the final defaults the Pi 5 shows 59.9 frames per second alone and still goes from 60 to about 31 (30.5–31.1) under an all-core load. The remaining cost is the GPU's time per frame, which goes from 1.5 ms alone to 14–16 ms under the load, while the clocks and the temperature (36.7–47.2 °C) show no clock or thermal throttling; memory contention between the GPU and the busy cores is the likely cause, not yet proven. The board's under-voltage alarm is present and read 0 with the official power supply. In a 3-minute all-core load with the fan the board kept 5.9 GFLOP/s at 55.6 °C at most, and it decodes 1080p video in software at 258 (H.264), 246 (HEVC), 204 (VP9) and 159 (AV1) frames per second.### 7.5 Modern PCs-There are no measurements on real PCs in the repository yet. The ISO is tested on virtual machines (UEFI and BIOS); testing on a real AMD machine from the live USB is planned. LordBench (0.8.6) is designed to measure memory and CPU at idle, boot time, frame times, video and app start in a repeatable way, and community hardware reports (0.8.7) to collect them from real machines (`docs/BENCHMARK.md`). In development for 0.8.6 (unreleased; the latest release is 0.8.5-beta), its first part is built: a sandboxed `lord-bench` helper that measures the CPU, memory, the GPU offscreen, storage and a sustained load, stops near the temperature limit or when the processor throttles, and records the conditions of each run, shown in System Information → Performance as "×N" of reference machines; it also measures software video decoding and the remote desktop's encoders, the desktop's frame times and the time from a pointer move to the screen, alone and under a low-priority load, and boot time over several restarts; it also runs from a terminal (`lordos-sysreport bench`). Also in development, it times LordOS's own interface work with the engine's real code (the layout and paint of a fixed full-HD desktop scene, and the shaping of paragraphs in Latin, Arabic, Devanagari, Thai and Chinese with fonts built into the helper, which opens no files; on the reference virtual machine 37 frames per second on one core and 40 with the paint threads, 619 shaping runs per second on one core and 3,595 on eight), compared with a reference only when it was measured with the same LordOS version, and `lord-bench` checks its own sandbox before any work: six things it must not be able to do (open a local socket or a network connection, run a program, start a process, create a file, read a system file) were all refused on that machine, and a run where one gets through is marked unstable. On a Raspberry Pi it watches the board's firmware during the whole run: the under-voltage alarm, the only flag the LordOS Pi kernel exposes, the firmware's full throttling flags where an older kernel has them, and 80 °C, where the firmware starts slowing the processor down, which stops a peak test as throttled; System Information's Raspberry Pi section reads the same alarm and flags and leaves out what the kernel doesn't show. This was tested on simulated system files, not yet on a real Pi. The references are a virtual machine and a Raspberry Pi 5 (§7.4); hardware video decoding and a real PC reference are not built yet.+There are no measurements on real PCs in the repository yet. The ISO is tested on virtual machines (UEFI and BIOS); testing on a real AMD machine from the live USB is planned. LordBench (0.8.6) is designed to measure memory and CPU at idle, boot time, frame times, video and app start in a repeatable way, and community hardware reports (0.8.7) to collect them from real machines (`docs/BENCHMARK.md`). In development for 0.8.6 (unreleased; the latest release is 0.8.5-beta), its first part is built: a sandboxed `lord-bench` helper that measures the CPU, memory, the GPU offscreen, storage and a sustained load, stops near the temperature limit or when the processor throttles, and records the conditions of each run, shown in System Information → Performance as "×N" of reference machines; it also measures software video decoding and the remote desktop's encoders, the desktop's frame times and the time from a pointer move to the screen, alone and under a low-priority load, and boot time over several restarts; it also runs from a terminal (`lordos-sysreport bench`). Also in development, it times LordOS's own interface work with the engine's real code (the layout and paint of a fixed full-HD desktop scene, and the shaping of paragraphs in Latin, Arabic, Devanagari, Thai and Chinese with fonts built into the helper, which opens no files; on the reference virtual machine 37 frames per second on one core and 40 with the paint threads, 619 shaping runs per second on one core and 3,595 on eight; on the Raspberry Pi 5, in two quick runs, 39 and 45 frames per second and 630 and 2,520 shaping runs per second on one and four cores), compared with a reference only when it was measured with the same LordOS version, and `lord-bench` checks its own sandbox before any work: six things it must not be able to do (open a local socket or a network connection, run a program, start a process, create a file, read a system file) were all refused on that machine, and a run where one gets through is marked unstable. On a Raspberry Pi it watches the board's firmware during the whole run: the under-voltage alarm, the only flag the LordOS Pi kernel exposes, the firmware's full throttling flags where an older kernel has them, and 80 °C, where the firmware starts slowing the processor down, which stops a peak test as throttled; System Information's Raspberry Pi section reads the same alarm and flags and leaves out what the kernel doesn't show. This was tested on simulated system files and on the Pi 5, where the alarm is present and reads 0 with the official power supply; an actual under-voltage was not provoked. The references are a virtual machine and a Raspberry Pi 5 (§7.4); hardware video decoding and a real PC reference are not built yet.### Source files@@ -701,7 +701,7 @@ There are no measurements on real PCs in the repository yet. The ISO is tested o- The package engine doesn't do i386 multiarch yet, so Steam isn't offered.- AI apps on a GPU: llama.cpp's Vulkan backend is untested on real AMD, NVIDIA and Intel hardware.- Dragging a window in 0.8.5-beta: small black squares can show at its rounded corners while it moves, on the monitor and in the remote desktop's frames (fixed for 0.8.6, in development, §7.2).-- On the Raspberry Pi 5 an app keeping every core busy still halves the desktop's frame rate (30 instead of 60 frames a second in LordBench's test, §7.4). <!-- PI-RESULT: §10.2, if the frame pipeline brings the Pi 5 under load near 60 fps, remove or reword this limitation with the measured number -->+- On the Raspberry Pi 5 an app keeping every core busy still halves the desktop's frame rate (about 31 instead of 60 frames a second in LordBench's test): the GPU's time per frame grows under the load, and the two changes measured for it in 0.8.6 (in development) gave too little and are off by default (§7.4).- Legacy BIOS boot: a black rectangle (GRUB's terminal area while it loads the kernel and the initrd) shows for a few seconds between the boot menu and the splash.- Wayland: no drag and drop, no LordOS input methods inside Linux apps (`text-input`), no `xdg-activation`, explicit sync, tearing control or tablets (§3.4).- Without a GPU, AV1 video at 60 fps is heavy, since the browser decodes it in software on the same machine.