Well it's because one of the specificity of EvolveOS Solus is to have more aggressive optimizations and faster boot than other classical distributions.Evertson wrote: ↑Fri Oct 13, 2017 9:16 pmGood evening everyone.
I really, yes really do not understand this whole discussion about speed. Once a day I startup my machine in 10, 20, 30 seconds. I do not care. The rest of the day my machine (with Solus for many years) is extremely fast. Most of the time I do my work in WPS spreadsheets. Sometimes more than 1000.000 rows (yes) and 50 colums. Solus does the job perfectly. So ( it's maybe my age, it's maybe my state of mind) but why the discussion about speed? Meanwhile making a cup of coffee or going to the toilet takes 100 times more time. But anyway : for many years Solus was, is and will be my favorite. Fast, stable, reliable and secure. So . SOLUS FOREVER. Whatever the startup time will be.
Greetings and have a nice weekend.
It was precisely a bit of fun when I started this post and to show off Solus' speed, it also get people talking on the forums a bit as well, which was the point of my other two posts (Where are you from?) and (What drew you to Solus?). They both just served to get people interacting more and discussing things.kyrios wrote: ↑Fri Oct 13, 2017 11:45 pmWell it's because one of the specificity of EvolveOS Solus is to have more aggressive optimizations and faster boot than other classical distributions.
I guess the topic was more a kind of game at the beginning, but it is also allow people to detect eventual problems in their boot sequence.
This is also a nice indicator to check how the boot time evolves over time (i.e: impact of new per-enabled services, of systemd upgrade, ...)
Also not everyone has the same usage of their computer. You say it is not important but people who use a slow laptop for example and who have to power it on and off multiple times a day for whatever reason may consider this as a very important criteria.
Code: Select all
systemd-analyze Startup finished in 3.884s (firmware) + 2.142s (loader) + 1.202s (kernel) + 3.820s (initrd) + 25.244s (userspace) = 36.294s
Code: Select all
systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @25.123s └─multi-user.target @25.123s └─systemd-resolved.service @24.958s +164ms └─network.target @24.957s └─NetworkManager.service @22.352s +2.604s └─dbus.service @20.442s └─basic.target @20.440s └─sockets.target @20.440s └─snapd.socket @20.421s +18ms └─sysinit.target @20.421s └─systemd-timesyncd.service @20.206s +214ms └─systemd-tmpfiles-setup.service @19.921s +264ms └─systemd-journal-flush.service @1.901s +18.019s └─systemd-remount-fs.service @1.526s +373ms └─systemd-fsck-root.service @584542y 2w 2d 20h 1min 48.184s +170ms └─systemd-journald.socket └─system.slice └─-.slice