You can trim some of that off pretty easily.

See this link here.

Much thanks for the link. I will post the results. In the meanwhile, I did a fresh install of the newly released LM 20, and the leak issue is gone.

Hmm... I thought systemd's big claim to fame was supposed to be the parallelization of service start up. Is there a switch to show all the tasks systemd is performing in parallel? "systemd-analyze critical-chain" is nice/interesting but it'd be great to know what other service startups are running at the same time as those that are contributing to the "critical chain". One could go to the trouble of disabling a particular startup step ("Huh? I don't need that!") only to find that there was another running in parallel that was only 1ms slower than the one you spent the time to track down and disable. Not that I need to do much tweaking what with my desktop reaching the graphical target in under 34s---I'd be lucky to get to the coffee pot and back in that time.

Aside: "systemd-analyze dot ..." generates a whole lot of useless for me. YMMV

There was a reduction in the boot time from 1.8 minutes to 54 seconds. Of course, worshipping the goddess of impatience is not a good thing.

I recently (just after the new year) used those tweaks on an older desktop that I wanted to give a buddy's friend. I threw in an SSD and had some spare RAM around so got it up to 8 GB. The boot time was under 30 seconds. My fuzzy memory says it was closer to 20 seconds with Ubuntu installed on it.

@ ineuw:-

I'm running an almost identical system to your own; in my case, a "Coffee Lake" G5400 @ 3.7 GHz , also with 16 GB of RAM. I run 'Puppy' Linux exclusively, and my boot times, using always ext3 - also with fsck enabled - are in the order of 25 seconds from power-on to a fully-settled down desktop. This is from a 7200 rpm 1 TB 'Toshie' mechanical spinner.

Bear in mind this is a 'frugal' system that runs entirely in RAM for the session, so that quoted 25 seconds includes creating a virtual file-system, copying the 'system' from 'read-only' files, and layering-in the aufs user 'save-folder' on top of everything. Puppy does this at every boot, uses sysvinit rather than systemd, and boots via Puppy's patched & regularly maintained 'special' version of the elderly Grub4DOS bootloader on a UEFI system....

Never mind getting to the kettle & back; I can't even get to the far end of the hall & back before she's straining at the leash & and eager to get on with things!

I'm quite happy with that. No complaints here.....


Mike.

The installation of a dedicated SSD drive reduced the boot time from grub to desktop to 15 seconds, including login. So, the issue is resolved. Thanks to all contributors.

Please remember to mark it as solved. It's up near the top of this page, kinda on the right, if memory serves.

I, for one, find the [Solved] marker to be a good help. It lets me know that the issue was resolved and the answer is potentially in that thread.