I have a system with many distros on it - several of them Arch based. Most of them boot quite quickly, ~5 seconds from selection at the boot loader screen. One, however, takes 50-55 seconds from the same point. I would prefer to figure out why, and perhaps eliminate the delay!
What I hope I can get is some direction to aim my searches, as I learn more than I ever thought to know (or want to!) about starting up a system. Here is a systemd-analyze blame which raises some possibilities:
Somewhat truncated, as I doubt any items further down are the source of the slowdown - but I would appreciate any pointers as to which to research first! One of possibilities is Network-Manager wait-online.service - but I’m running hardwired which my limited experience suggests should not be a slowdown.
Thanks for any directions to turn my attention to…
Well- I can’t say as I understand the contents entirely, but it doesn’t appear that lvmetad takes long…
15:18:27 WD= [~]
└───freebird@nest ─$ 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.
I quite like having it available - and I also like not ever needing it! But a physical swap partition, mounted in fstab, should be enough I would expect. I am guessing this was added for performance reasons (zswap?) but with consequences
Because I don’t need either, mainly - and a partition set up once, and used by all the different distros does not actually waste many resources needlessly. A swap file, on the other hand, would need to be set up on each system and would require me to be less lazy!