In case you're still interested, this is from the laptop
Code: Select all
[bill@laptop] ~/script $ systemd-analyze time
Startup finished in 8.523s (kernel) + 42.667s (userspace) = 51.191s
[bill@laptop] ~/script $
Code: Select all
[bill@laptop] ~/script $ systemd-analyze time
Startup finished in 8.523s (kernel) + 42.667s (userspace) = 51.191s
[bill@laptop] ~/script $
WharfRat, here is mine from PC:WharfRat wrote:riki,
In case you're still interested, this is from the laptop
Code: Select all
[bill@laptop] ~/script $ systemd-analyze time Startup finished in 8.523s (kernel) + 42.667s (userspace) = 51.191s [bill@laptop] ~/script $
Code: Select all
riki@riki-System-Product-Name ~ $ systemd-analyze time
Startup finished in 7.639s (kernel) + 33.077s (userspace) = 40.717s
riki@riki-System-Product-Name ~ $
Yes but a reboot or cold start takes just under 2 minutes for a working desktop!WharfRat wrote:It appears that yours is a lot quicker than mine
Would reaching userspace mean that you're 'there' on a headless system?riki wrote:Yes but a reboot or cold start takes just under 2 minutes for a working desktop!WharfRat wrote:It appears that yours is a lot quicker than mine
As I have said earlier the DE is reached in under 2 minutes. The motherboard takes about 20 seconds after which the LM logo (5 dots below) runs for about 30 seconds, then the cursor appears in about 20 seconds followed by user (me) which takes another 10 seconds (unless I click on it) and after that another delay before the DE is workable.greerd wrote:Would reaching userspace mean that you're 'there' on a headless system?riki wrote:Yes but a reboot or cold start takes just under 2 minutes for a working desktop!WharfRat wrote:It appears that yours is a lot quicker than mine
But in this case means starting the DE?
Code: Select all
murph@Murphs-laptop ~ $ systemd-analyze time
Startup finished in 3.680s (firmware) + 3.897s (loader) + 3.517s (kernel) + 9.253s (userspace) = 20.348s
murph@Murphs-laptop ~ $
murph@Murphs-laptop ~ $ systemd-analyze blame
1.776s nmbd.service
1.668s samba-ad-dc.service
1.659s NetworkManager.service
1.412s apparmor.service
1.412s NetworkManager-wait-online.service
1.156s dev-sda2.device
1.130s loadcpufreq.service
1.056s thermald.service
967ms ModemManager.service
948ms accounts-daemon.service
941ms colord.service
662ms lightdm.service
656ms systemd-tmpfiles-setup.service
579ms systemd-tmpfiles-clean.service
572ms networking.service
559ms gpu-manager.service
533ms upower.service
525ms systemd-rfkill.service
514ms grub-common.service
504ms virtualbox-guest-utils.service
497ms systemd-fsck@dev-disk-by\x2duuid-1406\x2d97F3.service
419ms lvm2-monitor.service
358ms console-kit-log-system-start.service
357ms console-setup.service
323ms rsyslog.service
271ms binfmt-support.service
267ms bluetooth.service
266ms ondemand.service
265ms systemd-logind.service
263ms speech-dispatcher.service
261ms irqbalance.service
251ms smbd.service
242ms systemd-user-sessions.service
240ms avahi-daemon.service
210ms wpa_supplicant.service
184ms plymouth-read-write.service
177ms ufw.service
162ms boot-efi.mount
154ms systemd-update-utmp.service
95ms keyboard-setup.service
93ms dev-sda3.swap
90ms systemd-journald.service
88ms lm-sensors.service
77ms systemd-udev-trigger.service
59ms polkitd.service
48ms setvtrgb.service
47ms systemd-tmpfiles-setup-dev.service
38ms systemd-modules-load.service
36ms udisks2.service
29ms systemd-udevd.service
27ms proc-sys-fs-binfmt_misc.mount
17ms alsa-restore.service
16ms user@1000.service
14ms plymouth-start.service
13ms systemd-sysctl.service
12ms systemd-journal-flush.service
12ms ntp.service
11ms hddtemp.service
11ms dev-mqueue.mount
9ms systemd-random-seed.service
8ms cpufrequtils.service
7ms systemd-remount-fs.service
5ms dns-clean.service
5ms pppd-dns.service
4ms rtkit-daemon.service
4ms kmod-static-nodes.service
3ms dev-hugepages.mount
3ms resolvconf.service
3ms sys-fs-fuse-connections.mount
3ms ureadahead-stop.service
2ms sys-kernel-debug.mount
2ms systemd-update-utmp-runlevel.service
2ms rc-local.service
2ms systemd-backlight@backlight:intel_backlight.service
2ms plymouth-quit-wait.service
1ms openvpn.service
riki wrote:How long is your boot time from cold start to desktop? Thanks.
Thanks but no, I am trying to find out if other people can boot quicker than me and reasons for it.MurphCID wrote:Is that the information that you wanted?
Wonderful! You really have something there. My time is 1 minute 30 seconds, start from cold or a restart makes no difference.Portreve wrote:I did a wipe and fresh install of LM 18.2 and there's no difference I can tell in performance. From the time it begins to boot to the login screen is for me maybe 10 seconds, iirc. Another five and I'm at the desktop.
riki wrote:Thanks but no, I am trying to find out if other people can boot quicker than me and reasons for it.MurphCID wrote:Is that the information that you wanted?
Thanks MurphCID but I would still want to know, in minutes and seconds, how long is your boot time from cold start to desktop or from a restart.MurphCID wrote:I have a Crucial MX300 275gb ssd and an Intel i3, in the computer if that helps. My standard boot times seem pretty quick for the most part, much faster than my 8 core Windows machine.....
riki wrote:Thanks but no, I am trying to find out if other people can boot quicker than me and reasons for it.MurphCID wrote:Is that the information that you wanted?
riki wrote:Thanks MurphCID but I would still want to know, in minutes and seconds, how long is your boot time from cold start to desktop or from a restart.MurphCID wrote:I have a Crucial MX300 275gb ssd and an Intel i3, in the computer if that helps. My standard boot times seem pretty quick for the most part, much faster than my 8 core Windows machine.....
riki wrote:
Thanks but no, I am trying to find out if other people can boot quicker than me and reasons for it.
20 seconds boot time? You must be joking!MurphCID wrote:I posted that above:
murph@Murphs-laptop ~ $ systemd-analyze time
Startup finished in 3.680s (firmware) + 3.897s (loader) + 3.517s (kernel) + 9.253s (userspace) = 20.348s
murph@Murphs-laptop ~ $
riki wrote:Thanks MurphCID but I would still want to know, in minutes and seconds, how long is your boot time from cold start to desktop or from a restart.MurphCID wrote:I have a Crucial MX300 275gb ssd and an Intel i3, in the computer if that helps. My standard boot times seem pretty quick for the most part, much faster than my 8 core Windows machine.....
riki wrote:20 seconds boot time? You must be joking!MurphCID wrote:I posted that above:
murph@Murphs-laptop ~ $ systemd-analyze time
Startup finished in 3.680s (firmware) + 3.897s (loader) + 3.517s (kernel) + 9.253s (userspace) = 20.348s
murph@Murphs-laptop ~ $
riki wrote:
Thanks MurphCID but I would still want to know, in minutes and seconds, how long is your boot time from cold start to desktop or from a restart.
I understand. Just simply time the boot time and tell me how long it takes. Forget the commands.MurphCID wrote:That is what that command gave me. I am so new, that I had to copy from here to get the proper command. I really don't know the command line very well. Like I said, it seems "snappier" now, so I have to go on what shows. I copied what came up in Terminal.
riki wrote:I understand. Just simply time the boot time and tell me how long it takes. Forget the commands.MurphCID wrote:That is what that command gave me. I am so new, that I had to copy from here to get the proper command. I really don't know the command line very well. Like I said, it seems "snappier" now, so I have to go on what shows. I copied what came up in Terminal.
That's excellent! Thank you.MurphCID wrote:OK, per my watch 25 seconds.
riki wrote:I understand. Just simply time the boot time and tell me how long it takes. Forget the commands.MurphCID wrote:That is what that command gave me. I am so new, that I had to copy from here to get the proper command. I really don't know the command line very well. Like I said, it seems "snappier" now, so I have to go on what shows. I copied what came up in Terminal.