#2

Images reach their desktop slower than aTerm's image did

Openoneamendezopened 8d ago

The release images still reach their desktop noticeably later than aTerm's Debian image did on crate. Not a blocker; recorded to look into later.

Measured on the iPhone Duo on 2026-11-13, from crate's "VM running" to a desktop on screen, with the same crate build and GPU path for every image:

ImageTo desktop
aTerm's Debian image (labwc + Xfce panel, started by a systemd service)3.1-3.3 s
Debian Xfce, stock as installed then (cloud-init on every boot)6.7 s
Debian Xfce, cloud-init switched off6.0-6.4 s
Debian Xfce, cloud-init off and the session's extras switched off4.9-5.0 s

Omarchy took about 23 s: its login screen waited for cloud-init's final stage on every boot (that stage ended at 19.6 s; the system itself was up at 5.7 s).

Already done, in arm64-desktop-images release 2026.11.14-4:

  • cloud-init runs on the first boot only, in every image.
  • "Debian Minimal" (debian-xfce-minimal) is Debian Xfce with the extras switched off: screen locker, colour management, network applet, sound server, Bonjour, and systemd-binfmt.

Where the rest of the time goes (Debian Xfce):

  • systemd-binfmt is on the critical path before the login screen, about 0.75 s, in every image except the minimal one.
  • The desktop session: X starts, LightDM opens an autologin session, then xfce4-session starts the window manager, panel and desktop in stages. aTerm's image skipped all of that: one root service started labwc, which launched the Xfce panel and desktop at once. That difference is about 1.8 s.

Not yet measured: KDE (Debian, Arch), Ubuntu GNOME, Arch Xfce and Omarchy since the 2026.11.14-4 release.

Ideas to try:

  • Measure every image since 2026.11.14-4, the same way.
  • Keep systemd-binfmt but take it off the login screen's critical path.
  • Per-desktop trims: KDE's Baloo indexer, GNOME's localsearch/tracker, Omarchy's CUPS.
  • An image that starts its desktop directly, as aTerm's did (Wayland, no display manager). Note Xfce on Wayland doesn't follow crate's display size changes yet.

How it was measured: a debug-only log line in crate when the display first shows a desktop, a launch argument that starts a given VM, and systemd-analyze plus process start times read over the serial console. That harness was deliberately not committed.

Activity

0

No activity yet.