I don't restart by systems or a browser all that often, so I honestly don't know how quickly that specific test is.
Comparing a bloated KDE to a lite-gnome2-ish isn't really fair, but for most users, switching distros is a good way to see what's possible. Most Ubuntu systems are bloated.
My main desktops begin with Ubuntu Server that has no GUI, only gets ssh install, then I build up the specific applications and services that I want.
From time to time, I'll load a stock version of Lubuntu, Xubuntu, Mate or the stock Ubuntu (gnome3) just to see what each team has done. Canonical definitely has an agenda to ensure every system has snap packages on it. The slightly different drivers could easily be why PopOS is working better for you. It would have been interesting to see the differences (for someone, not me), then perhaps we'd uncover what made it faster.
Many things go into choosing a distro. We are each different.
For fun, a few days ago I loaded Xubuntu 20.04 for a different need (actually trying to setup automatic desktop pushes for 50 clients). I didn't do anything related to performance testing. I think that system is still around somewhere. 2 CPU, 2G of RAM. SSD. I don't know if it has firefox.
11 seconds from boot to a login window.
4 seconds from password entry to full desktop.
4 seconds to start firefox until the full screen "Start here" was show.
Not really a high-power system:
Code:
$ inxi -b
System:
Host: xubu-2004 Kernel: 5.4.0-86-generic x86_64 bits: 64 Console: tty 1
Distro: Ubuntu 20.04.3 LTS (Focal Fossa)
Machine:
Type: Kvm System: QEMU product: Standard PC (i440FX + PIIX, 1996) v: pc-i440fx-bionic
serial: <superuser/root required>
Mobo: N/A model: N/A serial: N/A BIOS: SeaBIOS v: 1.10.2-1ubuntu1 date: 04/01/2014
CPU:
2x Single Core: AMD Ryzen 5 2600 type: SMP speed: 3394 MHz
Graphics:
Device-1: driver: bochs-drm v: N/A
Display: server: X.org 1.20.11 driver: modesetting unloaded: fbdev,vesa tty: 91x45
Message: Advanced graphics data unavailable in console. Try -G --display
Network:
Device-1: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus
Device-2: Red Hat Virtio network driver: virtio-pci
Drives:
Local Storage: total: 10.00 GiB used: 4.43 GiB (44.3%)
Info:
Processes: 203 Uptime: 14m Memory: 1.94 GiB used: 591.0 MiB (29.7%) Init: systemd
runlevel: 5 Shell: bash inxi: 3.0.38
$ free -h
total used free shared buff/cache available
Mem: 1.9Gi 500Mi 759Mi 9.0Mi 726Mi 1.3Gi
Swap: 1.0Gi 0B 1.0Gi
Using some tools that are built into all Ubuntus (systemd really) ...
Code:
$ systemd-analyze | tee perf.log
Startup finished in 2.758s (kernel) + 7.194s (userspace) = 9.952s
graphical.target reached after 6.347s in userspace
$ systemd-analyze blame | tee -a perf.log
1.407s systemd-udev-settle.service
1.118s dev-mapper-ubuntu\x2d\x2dvg\x2droot.device
1.081s systemd-networkd-wait-online.service
915ms udisks2.service
821ms cloud-init-local.service
682ms cloud-config.service
622ms accounts-daemon.service
477ms cloud-init.service
472ms networkd-dispatcher.service
464ms NetworkManager-wait-online.service
450ms ModemManager.service
450ms cloud-final.service
307ms NetworkManager.service
280ms systemd-timesyncd.service
279ms systemd-modules-load.service
257ms polkit.service
240ms systemd-logind.service
234ms lvm2-pvscan@252:3.service
216ms avahi-daemon.service
215ms keyboard-setup.service
209ms apparmor.service
186ms systemd-resolved.service
181ms switcheroo-control.service
171ms lvm2-monitor.service
143ms systemd-sysctl.service
142ms rsyslog.service
139ms multipathd.service
129ms systemd-journal-flush.service
126ms systemd-udevd.service
112ms apport.service
110ms wpa_supplicant.service
106ms grub-common.service
99ms e2scrub_reap.service
90ms dev-ubuntu\x2dvg-swap.swap
82ms user@1000.service
77ms systemd-udev-trigger.service
75ms systemd-networkd.service
....
$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @6.347s
└─udisks2.service @5.370s +915ms
└─basic.target @5.270s
└─sockets.target @5.269s
└─uuidd.socket @5.268s
└─sysinit.target @5.252s
└─cloud-init.service @4.728s +477ms
└─systemd-networkd-wait-online.service @3.643s +1.081s
└─systemd-networkd.service @3.567s +75ms
└─network-pre.target @3.565s
└─cloud-init-local.service @2.743s +821ms
└─systemd-remount-fs.service @855ms +19ms
└─systemd-journald.socket @789ms
└─-.mount @767ms
└─system.slice @767ms
└─-.slice @767ms
There's other stuff, but those are main things people can do something about without too much effort. I typically purge network-manager and avahi and all snap stuff, since I don't need/want them and they slow boots greatly.
You can see that with just 10G of storage, there won't be any data local to these systems.
lshw is useful to look for differences in hardware and settings and drivers. Just boot the fast system and save the output to a file, then boot the slow system and save the output to a different file, then use either system to compare the files - diff, sdiff, meld are all nice tools. People seem to really like meld. It is good to compare text files.
Bookmarks