Cauldron Boot Time - IRL

[kozaki]

Hi

I thought it'd be of interest to some of us around if we report boot times taken on various boxes powered by Mageia6 sta1, with Plasma5 and other desktops environments. Following are some (with links to details when they are known).

. . . . . OS . . . . . | . . D.E. . . | Date . | Time [1] . . . | Machine . . . . . . . | video | systemd-analyze
--------------------|-------------|----------|------------------|------------------------|----------|-----------------
Mageia6 sta1 | Plasma5 | Jul 10 | 65 (21 + 44) | Celeron 2007[2] | y
Mageia6 sta1 | Plasma5 | Jul 10 | 70 (35 + 35) | E 8400 hdd
Mageia6 sta1 | Plasma5 | Jul 10 | 70 (30 + 40) | i5 Sandy 2.3ghz hdd [4]
Mageia6 sta1 | Plasma5 | Jul 12 | 24 (10 + 14) | i3 Ivy 3.3 ghz ssd [4] | y
--------------------|-------------|----------|------------------|------------------------|----------|-----------------
Arch (rolling) | Plasma5 | Jul 10 | 54 . . . . . . . . . | Celeron 2007 . . . | y
Apricity rc1 . . | Gnome3| Jul 10 | 26 . . . . . . . . . | Celeron 2007 . . . | y
--------------------|-------------|----------|------------------|------------------------|----------|-----------------
Mageia6 sta1 | Mate . . . | Jul 11 | 18 (14 + 4) .. | Celeron 2007 . . . | y
Mageia6 sta1 | Mate . . . | Jul 12 | 24 (18 + 6) .. | Celeron 2007 . . . | y . . . | 19 sec
Mageia6 sta1 | Mate . . . | Jul 14 | 19 (13 + 6) .. | Celeron 2007 [4] | y . . . | 7.6 sec
Mageia6 sta1 | Mate . . . | Jul 22 | 7 . . . . . . . . . . | i3 Ivy 3.3 ghz ssd [4] | . | 3.4 sec (4.7.0-desktop-0.rc7.6.mga6)
Mageia6 sta1 | Mate . . . | Jul 27 | 8 . . . . . . . . . . | i3 Ivy 3.3 ghz ssd [4] | . | 6 sec (4.7.0-desktop-1.mga6)

Apologize for the quick and dirty vids with zaro cool pokemonGO audio track [3].

Errr... Despite being heavier on the RAM and CPU, GNOME give me the hand three times faster than Mageia6 Plasma5

Looking a bit where may that come from I noticed that Mageia6 set up the wrong IO scheduler (cfq, not noop or deadline) for the SSD. Beside I found zero udev rules and adding one in /etc/udev/rules.d/ has no effect. But maybe that's because of Qemu-kvm?

What about your timing, have you got enough time to go to ... while it boots?

To compare we just need the box's specs (cpu, ram and disk) and real time to boot to a usable desktop.
And to track the slowness factors we can use that command:

Code: Select all

uname -rms && systemd-analyze && systemd-analyze blame

EDIT: link to Corei3 Ivy corrected.
--
[1]: Seconds to a loaded desktop (from grub → login → desktop)
[2]: Celeron Conroe 1.9ghz, 2gig RAM and SSD in VM: `cpulimit -l 60% qemu-system-x86_64 -cpu Conroe -m 2G -enable-kvm`
[3]: I'd like to put the two screencasts side by side but unfortunately dunno how to
[4]: some daemons are disabled.

[ITA84]

Haven't timed it directly yet, but systemd-analyze reports about 37s (apparently there's a delay caused by NetworkManager Wait Online), and to that I'd add 30 to 40s for my Plasma5 desktop.

I'm on a fairly old laptop (HP Pavilion dv6 6020el) with an Intel i5 Sandy Bridge 2.3 GHz and a traditional HDD.

EDIT: measured properly and got about 48s to graphical system (I have autologin) and a total of 85s from grub to the Plasma5 desktop

[kozaki]

Ah I see. It seems Plasma 5 taking its optimization model after an old tractor.

I did a quick and dirty Arch / Plasma 5 DE install on the very same VM above. Takes just a bit less memory than mageia6 Beta1 but needs just the same time to launch :
Arch Plasma 5 boot time

[ITA84]

Well, for me Plasma5 startup time was never particularly fast; I used to disable Baloo and it was a little faster, but not by much. At the moment I have most standard session services active except for Akonadi. Please keep in mind though that I've been constantly upgrading Cauldron since Mageia 2, without ever reinstalling, so this could be a factor

[kozaki]

>this could be a factor

Or not, considering the freaking time (above) it takes on an ssd on a 1 week old fresh install.

For the record, Mate adds 3 seconds --or 15 less times to load than Plasma5-- on that same SSD install.

[kozaki]

ITA84 my last tests with Mate confirms your opinion on Plasma.

systemd-analyze && systemd-analyze blame

Code: Select all

Startup finished in 3.143s (kernel) + 4.952s (userspace) = 8.095s
          1.365s systemd-udev-settle.service
           915ms upower
           897ms mandriva-everytime.service
           895ms dev-sda1.device
           765 resolvconf.service
           731ms network.service
           679ms mga-bg-serv.service
           669ms msec.service
           588ms partmon.service
          ...

I can boot to the desktop; log in, open a libreoffice document, 2 web sites, some good music, an image and a vt then power off in 1'20. Check the video on post #1 for the OSes responsivity on such a light multi-tasking fast session.


systemd-analyze & blame on the Celeron COnroe @ 3.3 GHz give a smiling result

[kozaki]

Digging further in the auto-started services allows me to boot Mageia6-sta1 on my Celeron Conroe (single Core) 1.9ghz 2gig RAM and SSD in about the same time than with a much faster/multi-cores cpu. That's with the two kernels tested.

For comparison, on this set-up Cauldron default boots in:

Code: Select all

Startup finished in 3.676s (kernel) + 15.463s (userspace) = 19.140s

          4.086s network-up.service
          2.387s systemd-udev-settle.service
          2.163s mandriva-everytime.service
          1.541s network.service
           966ms resolvconf.service
           ...

graphical.target @15.453s         # "**" show the red lines
└─multi-user.target @15.453s
  └─**systemd-resolved.service @9.616s +99ms**
    └─network.target @9.612s
      └─**network-up.service @5.525s +4.086s**
        └─basic.target @5.518s
          └─**mandriva-everytime.service @3.354s +2.163s**
            └─local-fs.target @3.353s**
              └─**fedora-storage-init-late.service @3.312s +40ms**
                └─**fedora-storage-init.service @3.197s +114ms**
                  └─**fedora-wait-storage.service @3.182s +9ms**
                    └─**systemd-udev-settle.service @793ms +2.387s**
                      └─**systemd-udev-trigger.service @637ms +155ms**
                         ...
# Linux 4.6.3-desktop-1.mga6 i686 (2016-07-07)

Without iptable and shorewall services:

Code: Select all

Startup finished in 2.224s (kernel) + 11.995s (userspace) = 14.220s
          6.457s ntpdate.service
          2.437s network-up.service
          1.536s systemd-udev-settle.service
           726ms mandriva-everytime.service
           509ms dev-sda1.device
           ...
# Linux 4.7.0-desktop-0.rc7.1.mga6 i686

Now after configuring some services redondants (for my usages):

Code: Select all

Startup finished in 3.119s (kernel) + 4.447s (userspace) = 7.566s
          1.724s network.service
          1.121s dev-sda1.device
          1.117s partmon.service
          1.065s mga-bg-res.service
           806ms mandriva-save-dmesg.service
           ...
graphical.target @4.428s
└─multi-user.target @4.428s
  └─**network.service @2.703s +1.724s**
    └─basic.target @2.040s
      └─sockets.target @2.039s
        └─dbus.socket @2.039s
          └─sysinit.target @2.038s
            └─**systemd-update-utmp.service @2.013s +22ms**
              └─**systemd-tmpfiles-setup.service @1.909s +103ms**
                └─local-fs.target @1.747s
                  └─run-user-1000.mount @3.939s
                    └─local-fs-pre.target @840ms
                      └─**systemd-tmpfiles-setup-dev.service @722ms +117ms**
                        └─**kmod-static-nodes.service @439ms +65ms**
                          ...
# Linux 4.7.0-desktop-0.rc7.6.mga6 i686

Video screen
The video screen shows the *effective* speed to an functional Mate desktop. And that ~8 sec waiting time between grub and actually loading the system, that I have no idea what's causing it. Without the later, from grub to having my applications/files fully available would take just 14 seconds, on a nine years old mono core box. Do you have some idea what may cause this waiting time?

System's doing well (quite responsive!) and is very stable.

That one on a Core i3 Ivy @3.3 GHz 2gig RAM and SSD:

Code: Select all

Startup finished in 1.693s (kernel) + 1.716s (userspace) = 3.409s
           646ms network.service
           579ms dev-sda1.device
           272ms partmon.service
           ...
graphical.target @1.703s
└─multi-user.target @1.703s
  └─**network.service @1.056s +646ms**
    └─basic.target @848ms
      └─sockets.target @847ms
        └─dbus.socket @847ms
          └─sysinit.target @847ms
            └─**systemd-update-utmp.service @840ms +5ms**
              └─**systemd-tmpfiles-setup.service @803ms +29ms**
                └─local-fs.target @797ms
                  └─run-user-1000.mount @1.535s
                      ...
# Linux 4.7.0-desktop-0.rc7.6.mga6 i686

EDITed with latest rc kernel boot runtimes.

[kozaki]

With the new kernel-desktop-4.7.0, boot time has raised a bit according to systemd-analyze...:

Code: Select all

Linux 4.7.0-desktop-1.mga6 i686
Startup finished in 3.035s (kernel) + 2.921s (userspace) = 5.957s
          1.520s dev-sda1.device
           677ms systemd-vconsole-setup.service
           479ms mga-bg-res.service
           404ms systemd-user-sessions.service
           403ms acpid.service
           376ms upower.service
           354ms systemd-udev-trigger.service
           329ms systemd-udevd.service
           301ms systemd-journald.service
           285ms systemd-journal-flush.service
           270ms systemd-resolved.service
           232ms systemd-logind.service
           229ms rtkit-daemon.service
           195ms systemd-fsck-root.service
           174ms user@1000.service
           165ms mnt-data.mount
           157ms dev-disk-by-label-antiXswap.swap
           112ms sys-kernel-debug.mount
           111ms dev-mqueue.mount
           109ms udisks2.service
           104ms mandriva-save-dmesg.service
           102ms dev-hugepages.mount
            97ms systemd-tmpfiles-setup.service
            ...

...Though it does feel as fast as before otherwise: 8 sec clock timed from grub to Mate available on my Core i3 Ivy / SSD.