(01-04-2023, 02:24 AM)Jerry link Wrote: What is the output of:
Code:systemctl list-dependencies --reverse network-online.target
Sure, here's my output. Is there anything suspicious in it?
Code:
systemctl list-dependencies --reverse network-online.target network-online.target
● ├─cups-browsed.service
● ├─hddtemp.service
● ├─nmbd.service
● ├─packagekit.service
● └─smbd.service
(01-04-2023, 05:07 AM)stevef link Wrote:Quote:With third-party I am talking about the packages I tend to install ... I don't think it makes sense to post a full list of all my deps.
Do you notice the problem with the boot times of the machines prior to installing your third party packages ?
If I suspected third party package may be responsible I'd be doing analysis of boot ups before and after the third party stuff installation.
The boot time is evidently lost by an `apt update` call on if-up. So the third-parties that cause that delay can be best reported by the sources I'm going to look up on during this. In my case the firefox ppa is indeed a third-party. But any other repo that users may use, will cause further delays on everydays boot routines.
Code:
sudo apt update
[sudo] password for rew:
Hit:1 http://ubuntu.ethz.ch/ubuntu jammy InRelease
Hit:2 http://ubuntu.ethz.ch/ubuntu jammy-updates InRelease
Hit:3 http://ubuntu.ethz.ch/ubuntu jammy-backports InRelease
Hit:4 http://ubuntu.ethz.ch/ubuntu jammy-security InRelease
Hit:5 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease
Hit:6 http://archive.canonical.com/ubuntu jammy InRelease
Hit:7 http://repo.linuxliteos.com/linuxlite fluorite InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
9 packages can be upgraded. Run 'apt list --upgradable' to see them.
(01-04-2023, 02:34 AM)Jerry link Wrote: If this is your PC - http://www.hp.com/hpinfo/newsroom/press_..._6730b.pdf I wouldn't expect miracle boot times once the networking issue is resolved. Windows VistaYes, this is my PC ... it's pretty old. The full boot time, after the fix, is around 45 secs (including bios).Throw in an SSD (if possible) and tweak the boot, static IP helps a lot, and you should be in business.
See also my plots on the actual boot time (with the fix applied of course):
Code:
Startup finished in 6.053s (kernel) + 8.989s (userspace) = 15.043s graphical.target reached after 8.962s in userspace
So I'm happy with that. And yes it has an SSD. But actually I wasn't looking for advice how to make it faster: I've measured and isolated a clear problem, and want to share with other users how to get rid of it, or even better get it fixed in the linuxliteos distribution.
At any rate, we all know that a call of `apt update` doesn't come for free regardless of the disk. The more repos we're contacting the more this command delays the actual boot performance. We're making a real-world network operation.
My latest boot time measures are attached: today I only waste 10secs with it ... looks as if it highly depends on the activity on my network. What about if I'm connected to a slow network, having DNS problems, or a slow link, or using a slow mirror? The boot time will decrease almost beyond limits ... without any value for me as a user. That is not even a problem of old hardware ... but one of having a fast link to the web + mirrors.