LINUX.ORG.RU

История изменений

Исправление intelfx, (текущая версия) :

$ systemd-analyze
Startup finished in 13.595s (firmware) + 134ms (loader) + 497ms (kernel) + 2.062s (initrd) + 1.504s (userspace) = 17.795s

$ systemd-analyze blame | head -n10
          2.201s user@1000.service
          1.412s packagekit.service
           341ms ModemManager.service
           339ms home.mount
           227ms udisks2.service
           227ms systemd-modules-load.service
           205ms systemd-journal-flush.service
           181ms alsa-restore.service
           177ms geoclue.service
           172ms sshdgenkeys.service

$ 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 @1.503s
└─multi-user.target @1.502s
  └─ModemManager.service @1.159s +341ms
    └─basic.target @1.153s
      └─sockets.target @1.152s
        └─smbd.socket @1.151s
          └─sysinit.target @1.137s
            └─systemd-timesyncd.service @1.119s +16ms
              └─systemd-tmpfiles-setup.service @1.098s +15ms
                └─local-fs.target @1.096s
                  └─mnt-build.mount @1.025s +69ms
                    └─systemd-fsck@dev-disk-by\x2dlabel-linux\x2dbuild.service @1.020s +3ms
                      └─dev-disk-by\x2dlabel-linux\x2dbuild.device @1.019s

ThinkPad T540p, Liteon LSS-16L6G SSD, WDC WD10JPVX-08JC3T5 («Blue») HDD. Фирмварь — тормоз.

Исправление intelfx, :

$ systemd-analyze
Startup finished in 13.595s (firmware) + 134ms (loader) + 497ms (kernel) + 2.062s (initrd) + 1.504s (userspace) = 17.795s

$ systemd-analyze blame | head -n10
          2.201s user@1000.service
          1.412s packagekit.service
           341ms ModemManager.service
           339ms home.mount
           227ms udisks2.service
           227ms systemd-modules-load.service
           205ms systemd-journal-flush.service
           181ms alsa-restore.service
           177ms geoclue.service
           172ms sshdgenkeys.service

$ 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 @1.503s
└─multi-user.target @1.502s
  └─ModemManager.service @1.159s +341ms
    └─basic.target @1.153s
      └─sockets.target @1.152s
        └─smbd.socket @1.151s
          └─sysinit.target @1.137s
            └─systemd-timesyncd.service @1.119s +16ms
              └─systemd-tmpfiles-setup.service @1.098s +15ms
                └─local-fs.target @1.096s
                  └─mnt-build.mount @1.025s +69ms
                    └─systemd-fsck@dev-disk-by\x2dlabel-linux\x2dbuild.service @1.020s +3ms
                      └─dev-disk-by\x2dlabel-linux\x2dbuild.device @1.019s

ThinkPad T540p, Liteon LSS-16L6G SSD, WDC WD10JPVX-08JC3T5 («Blue») HDD.

Исходная версия intelfx, :

$ systemd-analyze
Startup finished in 13.595s (firmware) + 134ms (loader) + 497ms (kernel) + 2.062s (initrd) + 1.504s (userspace) = 17.795s

$ systemd-analyze blame | head -n10
          2.201s user@1000.service
          1.412s packagekit.service
           341ms ModemManager.service
           339ms home.mount
           227ms udisks2.service
           227ms systemd-modules-load.service
           205ms systemd-journal-flush.service
           181ms alsa-restore.service
           177ms geoclue.service
           172ms sshdgenkeys.service

ThinkPad T540p, Liteon LSS-16L6G SSD, WDC WD10JPVX-08JC3T5 («Blue») HDD.