 |
 |
 |
 |
| Fedora Focus Come in and have a general chat about Fedora and things relating to Fedora. |

16th February 2012, 05:15 PM
|
 |
Registered User
|
|
Join Date: Nov 2006
Location: Detroit
Posts: 4,616

|
|
|
How long does systemd take for you?
I was curious to see how much total time systemd takes to start all the services, since my boot times in Fedora with systemd are about 10-12 seconds longer than with the old SysV init system. So I looked at the systemd-analyze blame command and used awk to add up the times. Of course systemd starts services in parallel, so the sum of the individual times is far greater than the actual time it takes to boot (given by the systemd-analyze time command). But I thought it was interesting to see nonetheless. Here are the commands I ran:
Code:
systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
systemd-analyze time
and here's the output:
Code:
$ systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
16117ms remount-rootfs.service
12878ms systemd-vconsole-setup.service
10940ms media.mount
10854ms sys-kernel-debug.mount
10815ms dev-mqueue.mount
10023ms systemd-remount-api-vfs.service
8669ms fedora-storage-init.service
5769ms udev-settle.service
4109ms udev-trigger.service
4088ms udev.service
2861ms network.service
2270ms fedora-wait-storage.service
1979ms dkms_autoinstaller.service
1744ms systemd-sysctl.service
915ms console-kit-log-system-start.service
742ms gpm.service
672ms rsyslog.service
552ms lm_sensors.service
535ms systemd-readahead-collect.service
534ms systemd-readahead-replay.service
388ms fedora-storage-init-late.service
360ms gnustep.service
268ms sendmail.service
211ms fedora-readonly.service
175ms systemd-logind.service
160ms systemd-user-sessions.service
140ms dbus.service
126ms boot.mount
108ms xfs.service
74ms rc-local.service
59ms sm-client.service
46ms systemd-tmpfiles-setup.service
26ms vsftpd.service
18ms xinetd.service
34 services: Total = 109.225 seconds
$ systemd-analyze time
Startup finished in 1836ms (kernel) + 3633ms (initramfs) + 28530ms (userspace) = 34000ms
So it took 34 seconds to boot, despite all 34 services taking about 109 seconds.
Post your output here!
__________________
OS: Fedora 18 x86_64 | CPU: AMD64 3700+ 2.2GHz | RAM: 2GB PC3200 DDR | Disk: 160GB PATA | Video: ATI Radeon 7500 AGP 64MB | Sound: Turtle Beach Santa Cruz CS4630 | Ethernet: Realtek 8110SC
|

16th February 2012, 05:22 PM
|
 |
"Registered User" T-Shirt Winner
|
|
Join Date: Mar 2007
Location: Seville, FL
Posts: 5,121

|
|
|
Re: How long does systemd take for you?
On my i5-2500k desktop machine:
Code:
BASH:~/-> systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
5761ms var-lib-nfs-rpc_pipefs.mount
5390ms fedora-loadmodules.service
4786ms systemd-vconsole-setup.service
4172ms remount-rootfs.service
2969ms media.mount
2847ms sys-kernel-debug.mount
2826ms dev-mqueue.mount
2800ms sys-kernel-security.mount
2768ms dev-hugepages.mount
2764ms udev-trigger.service
2737ms udev.service
1979ms mdmonitor-takeover.service
1785ms systemd-remount-api-vfs.service
1650ms fedora-wait-storage.service
1534ms fedora-storage-init.service
1423ms sys-kernel-config.mount
1283ms udev-settle.service
1223ms jexec.service
1191ms NetworkManager.service
985ms systemd-sysctl.service
936ms rsyslog.service
902ms fedora-readonly.service
883ms systemd-logind.service
820ms avahi-daemon.service
688ms iptables.service
686ms console-kit-log-system-start.service
683ms ip6tables.service
662ms mcelog.service
652ms auditd.service
618ms lm_sensors.service
587ms irqbalance.service
569ms systemd-readahead-collect.service
537ms systemd-readahead-replay.service
525ms sshd-keygen.service
517ms abrt-ccpp.service
513ms abrt-vmcore.service
461ms dbus.service
379ms proc-sys-fs-binfmt_misc.mount
212ms fedora-storage-init-late.service
169ms netfs.service
164ms livesys.service
162ms nfs-lock.service
142ms nfs-idmap.service
124ms fcoe.service
98ms boot.mount
85ms rc-local.service
76ms systemd-tmpfiles-setup.service
69ms sandbox.service
62ms rpcbind.service
53ms systemd-user-sessions.service
51ms lvm2-monitor.service
47ms livesys-late.service
42ms home.mount
42ms console-kit-daemon.service
6ms accounts-daemon.service
4ms rtkit-daemon.service
56 services: Total = 66.099 seconds
BASH:~/-> systemd-analyze time
Startup finished in 1439ms (kernel) + 2625ms (initramfs) + 12833ms (userspace) = 16898ms
|

16th February 2012, 05:28 PM
|
 |
'The Blue Dragon'
|
|
Join Date: Jan 2011
Location: chennai
Posts: 988

|
|
|
Re: How long does systemd take for you?
Code:
systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
Total = 95.551 seconds
Code:
[candice@localhost ~]$ systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
7641ms iscsi.service
7099ms remount-rootfs.service
6858ms media.mount
6835ms dev-mqueue.mount
6815ms dev-hugepages.mount
6813ms sys-kernel-security.mount
6795ms sys-kernel-debug.mount
6620ms fedora-loadmodules.service
4641ms udev-trigger.service
4194ms mdmonitor-takeover.service
4133ms udev.service
3875ms systemd-remount-api-vfs.service
3602ms systemd-vconsole-setup.service
3392ms sys-kernel-config.mount
3122ms udev-settle.service
2248ms iscsid.service
2180ms netfs.service
1898ms fcoe.service
649ms NetworkManager.service
579ms bluetooth.service
431ms avahi-daemon.service
411ms systemd-readahead-collect.service
394ms systemd-readahead-replay.service
366ms rsyslog.service
350ms console-kit-log-system-start.service
327ms systemd-logind.service
323ms fedora-storage-init.service
294ms chronyd.service
265ms iptables.service
259ms ip6tables.service
235ms mcelog.service
232ms auditd.service
205ms irqbalance.service
198ms sshd-keygen.service
162ms systemd-tmpfiles-setup.service
155ms dbus.service
138ms fedora-readonly.service
117ms livesys.service
106ms fedora-storage-init-late.service
106ms sm-client.service
76ms lvm2-monitor.service
65ms console-kit-daemon.service
64ms sandbox.service
64ms systemd-sysctl.service
59ms sendmail.service
52ms fedora-wait-storage.service
44ms accounts-daemon.service
26ms rtkit-daemon.service
23ms livesys-late.service
8ms sys-fs-fuse-connections.mount
7ms systemd-user-sessions.service
51 services: Total = 95.551 seconds
[candice@localhost ~]$
Code:
systemd-analyze time
Code:
Startup finished in 2277ms (kernel) + 3964ms (initramfs) + 20650ms (userspace) = 26892ms
__________________
LENOVO Y580 FHD Intel® Core™ i7-3630QM CPU @ 2.40GHz × 8 |660M GTX NVIDIA | 120 GB SSD OCZ AGILITY Fedora
|

16th February 2012, 05:30 PM
|
 |
Administrator
|
|
Join Date: Aug 2009
Posts: 6,613

|
|
|
Re: How long does systemd take for you?
well, on one of my older 1.8GHz dual core machines:
Code:
[root@tower20 ~]# systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
20059ms nfs-idmap.service
19691ms var-lib-nfs-rpc_pipefs.mount
19690ms fedora-loadmodules.service
15298ms systemd-vconsole-setup.service
13158ms udev-settle.service
12897ms udev.service
10056ms fedora-readonly.service
8113ms udev-trigger.service
7344ms remount-rootfs.service
5396ms media.mount
5065ms mdmonitor-takeover.service
4999ms dev-hugepages.mount
4987ms sys-kernel-security.mount
4973ms sys-kernel-debug.mount
4961ms dev-mqueue.mount
4323ms systemd-remount-api-vfs.service
4018ms systemd-sysctl.service
2926ms fedora-storage-init.service
1962ms sys-kernel-config.mount
724ms systemd-readahead-collect.service
701ms systemd-readahead-replay.service
545ms netfs.service
464ms fedora-storage-init-late.service
395ms mnt-Drive_J.mount
343ms rsyslog.service
322ms console-kit-log-system-start.service
299ms systemd-logind.service
287ms chronyd.service
276ms NetworkManager.service
254ms avahi-daemon.service
235ms auditd.service
223ms acpid.service
220ms lvm2-monitor.service
217ms sshd-keygen.service
217ms mcelog.service
187ms gpm.service
184ms systemd-tmpfiles-setup.service
183ms home.mount
174ms irqbalance.service
144ms mnt-t11c.mount
126ms mnt-t11d.mount
120ms mnt-t11e.mount
104ms mnt-t11f.mount
99ms nfs-lock.service
91ms mnt-t11g.mount
91ms dbus.service
90ms boot.mount
82ms xinetd.service
79ms mnt-t11h.mount
66ms mnt-t11i.mount
47ms console-kit-daemon.service
43ms fedora-wait-storage.service
26ms systemd-user-sessions.service
18ms rpcbind.service
8ms accounts-daemon.service
6ms rtkit-daemon.service
56 services: Total = 177.606 seconds
[root@tower20 ~]# systemd-analyze time
Startup finished in 1652ms (kernel) + 2687ms (initramfs) + 70901ms (userspace) = 75241ms
Now it starts GDM in a little over 33 seconds, and the NFS mounts continue on while GDM is loading, so it doesn't appear to take as long as it states.
I have noticed that in the past 2-3 weeks, something updated and it takes about 5-10 seconds longer to boot than it did. I don't know if it was a systemd update or one of the kernel updates that did it.
|

16th February 2012, 05:41 PM
|
 |
'The Blue Dragon'
|
|
Join Date: Jan 2011
Location: chennai
Posts: 988

|
|
|
Re: How long does systemd take for you?
As rupert says, fedora has slowed a bit, since f15,with systemd.
maybe not becoz of systemd.Probably due to heavier packages.
But my current arch linux 'BSD-init style' boot times are way faster than my fedora. probably 10 sec difference.Maybe becoz I have not got all the packages in archlinux loaded that fedora loads up by default during the boot.
__________________
LENOVO Y580 FHD Intel® Core™ i7-3630QM CPU @ 2.40GHz × 8 |660M GTX NVIDIA | 120 GB SSD OCZ AGILITY Fedora
|

16th February 2012, 10:23 PM
|
 |
Registered User
|
|
Join Date: Apr 2006
Location: North West UK.
Age: 32
Posts: 510

|
|
|
Re: How long does systemd take for you?
Here is mine.
Code:
systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
14833ms ntpdate.service
1388ms netfs.service
1348ms sendmail.service
1288ms iscsi.service
930ms rsyslog.service
733ms fedora-storage-init.service
719ms jexec.service
614ms bluetooth.service
524ms sm-client.service
487ms udev-settle.service
449ms fedora-storage-init-late.service
442ms systemd-logind.service
402ms NetworkManager.service
394ms lm_sensors.service
385ms plymouth-start.service
380ms console-kit-log-system-start.service
344ms abrt-vmcore.service
336ms ksm.service
335ms gpm.service
334ms mcelog.service
326ms downloads.mount
321ms sshd-keygen.service
286ms dbus.service
245ms proc-sys-fs-binfmt_misc.mount
237ms nfs-lock.service
187ms systemd-readahead-collect.service
187ms udev-trigger.service
181ms libvirtd.service
172ms iscsid.service
171ms systemd-readahead-replay.service
153ms archive.mount
131ms sandbox.service
122ms media.mount
114ms remount-rootfs.service
112ms systemd-remount-api-vfs.service
112ms fedora-loadmodules.service
111ms fedora-wait-storage.service
106ms boot.mount
98ms var-lib-nfs-rpc_pipefs.mount
95ms systemd-sysctl.service
86ms vboxdrv.service
85ms xinetd.service
83ms vboxballoonctrl-service.service
79ms fedora-readonly.service
79ms dev-mqueue.mount
78ms systemd-vconsole-setup.service
75ms nfs-idmap.service
68ms dev-hugepages.mount
56ms sys-kernel-security.mount
54ms home.mount
51ms libvirt-guests.service
51ms lvm2-monitor.service
37ms sys-kernel-debug.mount
36ms twonkywebdavserver.service
35ms rpcbind.service
33ms console-kit-daemon.service
33ms systemd-tmpfiles-setup.service
30ms rc-local.service
30ms vboxweb-service.service
27ms preload.service
26ms livesys.service
26ms livesys-late.service
24ms ksmtuned.service
23ms twonkyserver.service
23ms systemd-user-sessions.service
19ms udev.service
11ms sys-kernel-config.mount
9ms accounts-daemon.service
4ms rtkit-daemon.service
0ms sys-fs-fuse-connections.mount
70 services: Total = 31.403 seconds
[yeok@yeok ~]$ systemd-analyze time
Startup finished in 1611ms (kernel) + 1349ms (initramfs) + 18372ms (userspace) = 21334ms
__________________
He who asks a question is a fool for a minute; he who does not remains a fool forever.
|

16th February 2012, 10:57 PM
|
 |
Registered User
|
|
Join Date: Jun 2004
Location: Laurel, MD USA
Posts: 5,448

|
|
|
Re: How long does systemd take for you?
Quote:
Originally Posted by YeOK
Here is mine.
Code:
systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
14833ms ntpdate.service
1388ms netfs.service
1348ms sendmail.service
1288ms iscsi.service
930ms rsyslog.service
733ms fedora-storage-init.service
719ms jexec.service
614ms bluetooth.service
524ms sm-client.service
487ms udev-settle.service
449ms fedora-storage-init-late.service
442ms systemd-logind.service
402ms NetworkManager.service
394ms lm_sensors.service
385ms plymouth-start.service
380ms console-kit-log-system-start.service
344ms abrt-vmcore.service
336ms ksm.service
335ms gpm.service
334ms mcelog.service
326ms downloads.mount
321ms sshd-keygen.service
286ms dbus.service
245ms proc-sys-fs-binfmt_misc.mount
237ms nfs-lock.service
187ms systemd-readahead-collect.service
187ms udev-trigger.service
181ms libvirtd.service
172ms iscsid.service
171ms systemd-readahead-replay.service
153ms archive.mount
131ms sandbox.service
122ms media.mount
114ms remount-rootfs.service
112ms systemd-remount-api-vfs.service
112ms fedora-loadmodules.service
111ms fedora-wait-storage.service
106ms boot.mount
98ms var-lib-nfs-rpc_pipefs.mount
95ms systemd-sysctl.service
86ms vboxdrv.service
85ms xinetd.service
83ms vboxballoonctrl-service.service
79ms fedora-readonly.service
79ms dev-mqueue.mount
78ms systemd-vconsole-setup.service
75ms nfs-idmap.service
68ms dev-hugepages.mount
56ms sys-kernel-security.mount
54ms home.mount
51ms libvirt-guests.service
51ms lvm2-monitor.service
37ms sys-kernel-debug.mount
36ms twonkywebdavserver.service
35ms rpcbind.service
33ms console-kit-daemon.service
33ms systemd-tmpfiles-setup.service
30ms rc-local.service
30ms vboxweb-service.service
27ms preload.service
26ms livesys.service
26ms livesys-late.service
24ms ksmtuned.service
23ms twonkyserver.service
23ms systemd-user-sessions.service
19ms udev.service
11ms sys-kernel-config.mount
9ms accounts-daemon.service
4ms rtkit-daemon.service
0ms sys-fs-fuse-connections.mount
70 services: Total = 31.403 seconds
[yeok@yeok ~]$ systemd-analyze time
Startup finished in 1611ms (kernel) + 1349ms (initramfs) + 18372ms (userspace) = 21334ms
|
There's a pretty good chance that you can turn off the services I bolded in the list. Although ntpdate has a
use, Fedora 16 uses chrony and I think in most normal uses, it should fix the clock drift ok without the
ntpdate 'one shot' update at boot time
|

17th February 2012, 12:11 AM
|
 |
Registered User
|
|
Join Date: Sep 2009
Posts: 1,409

|
|
|
Re: How long does systemd take for you?
Code:
$ systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
60453ms sm-client.service
60292ms sendmail.service
26617ms fedora-loadmodules.service
25504ms systemd-vconsole-setup.service
15757ms media.mount
15735ms dev-mqueue.mount
15728ms sys-kernel-security.mount
15720ms udev-trigger.service
15720ms dev-hugepages.mount
15714ms sys-kernel-debug.mount
15602ms remount-rootfs.service
14359ms sys-kernel-config.mount
13802ms mdmonitor-takeover.service
13734ms udev.service
13324ms systemd-remount-api-vfs.service
13118ms udev-settle.service
8952ms fedora-readonly.service
1970ms systemd-sysctl.service
1768ms fedora-storage-init.service
974ms media-Users.mount
951ms NetworkManager.service
690ms netfs.service
685ms rsyslog.service
562ms chronyd.service
460ms console-kit-log-system-start.service
427ms systemd-logind.service
424ms ip6tables.service
420ms iptables.service
409ms mateaccounts-daemon.service
403ms auditd.service
383ms plymouth-start.service
371ms avahi-daemon.service
362ms lm_sensors.service
354ms fedora-storage-init-late.service
347ms irqbalance.service
321ms acpid.service
296ms nfs-lock.service
295ms abrt-ccpp.service
261ms mcelog.service
259ms abrt-vmcore.service
254ms sshd-keygen.service
232ms var.mount
222ms dbus.service
218ms boot.mount
215ms systemd-tmpfiles-setup.service
214ms home.mount
213ms nfs-idmap.service
180ms sandbox.service
157ms systemd-readahead-collect.service
127ms systemd-readahead-replay.service
83ms lvm2-monitor.service
52ms console-kit-daemon.service
50ms fedora-wait-storage.service
36ms var-lib-nfs-rpc_pipefs.mount
30ms var-tmp.mount
27ms rpcbind.service
12ms tmp.mount
11ms accounts-daemon.service
10ms systemd-user-sessions.service
8ms rtkit-daemon.service
0ms sys-fs-fuse-connections.mount
61 services: Total = 375.874 seconds
$ systemd-analyze time
Startup finished in 1455ms (kernel) + 5242ms (initramfs) + 154904ms (userspace) = 161603ms
I think I need to optimize my boot up.
dd_wizard
---------- Post added at 04:11 PM ---------- Previous post was at 04:09 PM ----------
I just remembered I had to manually connect to a new hot spot on that boot. I'll post more typical results later.
dd_wizard
|

17th February 2012, 12:40 AM
|
|
Registered User
|
|
Join Date: Jan 2006
Posts: 2,769

|
|
|
Re: How long does systemd take for you?
For the sendmail and sm services taking a full minute you just need to add your hostname to the end of both ipv4 and ipv6 lines in /etc/hosts. Even though they take that long to start those two don't slow down the boot.
|

17th February 2012, 01:50 AM
|
 |
Registered User
|
|
Join Date: Sep 2009
Posts: 1,409

|
|
|
Re: How long does systemd take for you?
Quote:
Originally Posted by JEO
For the sendmail and sm services taking a full minute you just need to add your hostname to the end of both ipv4 and ipv6 lines in /etc/hosts. Even though they take that long to start those two don't slow down the boot.
|
Thanks, JEO. I did that once way back when I originally installed F12. I've been upgrading with yum until F16 and completely forgot about that.
dd_wizard
---------- Post added at 05:50 PM ---------- Previous post was at 05:42 PM ----------
Here are the numbers after following JEO's advice:
Code:
$ systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
22869ms fedora-loadmodules.service
21840ms remount-rootfs.service
20115ms media.mount
20095ms dev-mqueue.mount
20081ms sys-kernel-security.mount
20073ms dev-hugepages.mount
20065ms sys-kernel-debug.mount
19365ms systemd-vconsole-setup.service
18347ms sys-kernel-config.mount
16627ms udev-trigger.service
16601ms udev.service
14905ms mdmonitor-takeover.service
14775ms systemd-remount-api-vfs.service
7755ms udev-settle.service
3042ms fedora-storage-init.service
1775ms systemd-sysctl.service
1108ms fedora-readonly.service
940ms fedora-storage-init-late.service
850ms NetworkManager.service
710ms fedora-wait-storage.service
687ms netfs.service
618ms rsyslog.service
597ms nfs-lock.service
572ms var.mount
484ms chronyd.service
456ms boot.mount
426ms lvm2-monitor.service
420ms console-kit-log-system-start.service
391ms ip6tables.service
386ms iptables.service
372ms media-Users.mount
356ms auditd.service
346ms systemd-logind.service
321ms mateaccounts-daemon.service
316ms systemd-tmpfiles-setup.service
302ms irqbalance.service
295ms lm_sensors.service
293ms avahi-daemon.service
265ms home.mount
263ms acpid.service
237ms abrt-ccpp.service
216ms abrt-vmcore.service
215ms mcelog.service
212ms sshd-keygen.service
183ms dbus.service
154ms systemd-readahead-collect.service
143ms sandbox.service
125ms sm-client.service
124ms systemd-readahead-replay.service
87ms sendmail.service
69ms console-kit-daemon.service
55ms nfs-idmap.service
31ms var-lib-nfs-rpc_pipefs.mount
30ms rpcbind.service
19ms systemd-user-sessions.service
13ms var-tmp.mount
11ms tmp.mount
8ms rtkit-daemon.service
6ms accounts-daemon.service
59 services: Total = 272.042 seconds
$ systemd-analyze time
Startup finished in 1447ms (kernel) + 5471ms (initramfs) + 35076ms (userspace) = 41996ms
|

17th February 2012, 07:20 PM
|
 |
Registered User
|
|
Join Date: Apr 2006
Location: North West UK.
Age: 32
Posts: 510

|
|
|
Re: How long does systemd take for you?
Quote:
Originally Posted by marko
There's a pretty good chance that you can turn off the services I bolded in the list. Although ntpdate has a
use, Fedora 16 uses chrony and I think in most normal uses, it should fix the clock drift ok without the
ntpdate 'one shot' update at boot time
|
Thanks, I shall give it a go later. I actually use Bluetooth so that service would need to stay. I'll update the post to show what difference the changes make.
Update:
Code:
systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
1329ms netfs.service
869ms fedora-storage-init.service
741ms jexec.service
659ms rsyslog.service
576ms bluetooth.service
568ms udev-settle.service
418ms NetworkManager.service
402ms console-kit-log-system-start.service
351ms ksm.service
349ms systemd-logind.service
338ms lm_sensors.service
335ms fedora-storage-init-late.service
315ms mcelog.service
294ms abrt-vmcore.service
293ms sshd-keygen.service
276ms gpm.service
239ms systemd-readahead-collect.service
216ms dbus.service
215ms downloads.mount
201ms systemd-readahead-replay.service
200ms dev-hugepages.mount
182ms proc-sys-fs-binfmt_misc.mount
170ms media.mount
167ms udev-trigger.service
164ms sys-kernel-security.mount
147ms var-lib-nfs-rpc_pipefs.mount
131ms sys-kernel-debug.mount
131ms dev-mqueue.mount
128ms libvirtd.service
122ms nfs-lock.service
121ms archive.mount
105ms vboxdrv.service
103ms fedora-readonly.service
99ms udev.service
94ms systemd-remount-api-vfs.service
94ms remount-rootfs.service
93ms fedora-loadmodules.service
92ms twonkyserver.service
84ms systemd-sysctl.service
72ms systemd-vconsole-setup.service
72ms preload.service
70ms lvm2-monitor.service
67ms systemd-tmpfiles-setup.service
57ms vboxweb-service.service
53ms fedora-wait-storage.service
51ms xinetd.service
49ms boot.mount
41ms nfs-idmap.service
34ms sandbox.service
31ms vboxballoonctrl-service.service
30ms libvirt-guests.service
30ms rc-local.service
30ms systemd-user-sessions.service
30ms home.mount
30ms console-kit-daemon.service
25ms livesys.service
25ms livesys-late.service
20ms rpcbind.service
17ms ksmtuned.service
14ms accounts-daemon.service
13ms twonkywebdavserver.service
12ms sys-kernel-config.mount
6ms rtkit-daemon.service
0ms sys-fs-fuse-connections.mount
64 services: Total = 12.29 seconds
[yeok@yeok ~]$ systemd-analyze time
Startup finished in 1573ms (kernel) + 1345ms (initramfs) + 8456ms (userspace) = 11375ms
Made quite a difference. I also added my host name to the host files. Thanks for the advice Marko.
__________________
He who asks a question is a fool for a minute; he who does not remains a fool forever.
Last edited by YeOK; 18th February 2012 at 11:01 AM.
|

16th February 2012, 10:37 PM
|
 |
Registered User
|
|
Join Date: Aug 2010
Location: Wellington, New Zealand
Age: 16
Posts: 889

|
|
|
Re: How long does systemd take for you?
This used to take 1:12, but I've disabled a few services
Code:
16504ms udev-settle.service
10389ms fedora-loadmodules.service
5155ms media.mount
5133ms dev-mqueue.mount
5116ms dev-hugepages.mount
5089ms remount-rootfs.service
5086ms sys-kernel-security.mount
5052ms sys-kernel-debug.mount
4725ms udev-trigger.service
4095ms udev.service
3619ms systemd-remount-api-vfs.service
3188ms systemd-vconsole-setup.service
2861ms sys-kernel-config.mount
1629ms fedora-readonly.service
814ms NetworkManager.service
715ms iscsid.service
657ms fedora-storage-init.service
606ms netfs.service
562ms avahi-daemon.service
469ms rsyslog.service
425ms systemd-logind.service
415ms console-kit-log-system-start.service
357ms sandbox.service
354ms iptables.service
347ms ip6tables.service
336ms mcelog.service
327ms auditd.service
314ms dbus.service
303ms systemd-readahead-collect.service
300ms abrt-vmcore.service
291ms irqbalance.service
287ms systemd-readahead-replay.service
283ms sshd-keygen.service
229ms abrt-ccpp.service
216ms systemd-tmpfiles-setup.service
168ms fedora-storage-init-late.service
159ms home.mount
97ms systemd-sysctl.service
89ms console-kit-daemon.service
89ms atieventsd.service
75ms fcoe.service
72ms fedora-wait-storage.service
25ms systemd-user-sessions.service
16ms rtkit-daemon.service
11ms accounts-daemon.service
0ms sys-fs-fuse-connections.mount
46 services: Total = 87.049 seconds
__________________
"For what is a man profited if he gains the whole world, but loses his own soul?"
- Jesus
|

17th February 2012, 01:04 AM
|
 |
Retired Administrator
|
|
Join Date: Oct 2006
Posts: 21,509

|
|
|
Re: How long does systemd take for you?
Here's my results
Code:
[leigh@main_pc ~]$ systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
1100ms rsyslog.service
1016ms NetworkManager.service
969ms netfs.service
806ms avahi-daemon.service
746ms udev-settle.service
698ms systemd-logind.service
631ms fedora-storage-init.service
587ms chronyd.service
552ms iptables.service
526ms console-kit-log-system-start.service
524ms auditd.service
509ms acpid.service
496ms irqbalance.service
382ms sshd-keygen.service
377ms systemd-binfmt.service
376ms nfs-server.service
372ms mcelog.service
370ms dbus.service
348ms systemd-readahead-replay.service
318ms udev-trigger.service
317ms systemd-readahead-collect.service
219ms systemd-remount-api-vfs.service
219ms media.mount
217ms remount-rootfs.service
212ms fedora-loadmodules.service
202ms udev.service
190ms sys-kernel-security.mount
182ms systemd-sysctl.service
165ms dev-mqueue.mount
145ms home.mount
142ms home-leigh-development.mount
137ms fedora-storage-init-late.service
129ms proc-sys-fs-binfmt_misc.mount
128ms systemd-vconsole-setup.service
127ms sys-kernel-debug.mount
119ms home-leigh-qBT_dir.mount
116ms home-leigh-data.mount
110ms systemd-tmpfiles-setup.service
105ms fedora-readonly.service
103ms dev-hugepages.mount
95ms fedora-wait-storage.service
95ms rpcbind.service
91ms nfs-lock.service
90ms proc-fs-nfsd.mount
90ms sys-kernel-config.mount
81ms nmb.service
75ms smb.service
67ms jexec.service
67ms nfs-idmap.service
66ms var-lib-nfs-rpc_pipefs.mount
52ms console-kit-daemon.service
42ms systemd-user-sessions.service
24ms home-leigh-data1.mount
23ms tmp.mount
10ms accounts-daemon.service
7ms rtkit-daemon.service
1ms sys-fs-fuse-connections.mount
57 services: Total = 15.963 seconds
[leigh@main_pc ~]$ systemd-analyze time
Startup finished in 3804ms (kernel) + 1825ms (initramfs) + 5975ms (userspace) = 11605ms
[leigh@main_pc ~]$
|

17th February 2012, 03:15 AM
|
 |
Registered User
|
|
Join Date: May 2009
Location: Manorville, New York, USA
Posts: 1,577

|
|
|
Re: How long does systemd take for you?
Code:
[GoinEasy9@fedora16dwkde ~]$ systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
4944ms fedora-loadmodules.service
4296ms media.mount
4260ms dev-mqueue.mount
4232ms sys-kernel-debug.mount
4220ms remount-rootfs.service
4198ms dev-hugepages.mount
4173ms sys-kernel-security.mount
4123ms var-lib-nfs-rpc_pipefs.mount
2734ms udev-settle.service
2598ms mdmonitor-takeover.service
2444ms udev-trigger.service
2369ms udev.service
2273ms systemd-remount-api-vfs.service
2006ms systemd-vconsole-setup.service
1808ms systemd-sysctl.service
1765ms sys-kernel-config.mount
1492ms iscsi.service
876ms NetworkManager.service
725ms rsyslog.service
698ms avahi-daemon.service
680ms fedora-readonly.service
650ms systemd-logind.service
563ms fedora-wait-storage.service
553ms systemd-readahead-collect.service
514ms lm_sensors.service
507ms ip6tables.service
496ms mcelog.service
494ms systemd-readahead-replay.service
487ms irqbalance.service
483ms iptables.service
481ms auditd.service
474ms console-kit-log-system-start.service
464ms livesys.service
459ms dbus.service
441ms acpid.service
424ms sshd-keygen.service
408ms abrt-ccpp.service
388ms abrt-vmcore.service
342ms systemd-tmpfiles-setup.service
253ms fedora-storage-init.service
196ms sm-client.service
175ms netfs.service
174ms nfs-lock.service
170ms iscsid.service
154ms sendmail.service
149ms rtkit-daemon.service
112ms sandbox.service
105ms boot.mount
100ms fcoe.service
96ms fedora-storage-init-late.service
75ms home.mount
70ms lvm2-monitor.service
62ms rpcbind.service
57ms console-kit-daemon.service
52ms systemd-user-sessions.service
46ms nfs-idmap.service
31ms livesys-late.service
0ms sys-fs-fuse-connections.mount
58 services: Total = 67.619 seconds
[GoinEasy9@fedora16dwkde ~]$ systemd-analyze time
Startup finished in 1474ms (kernel) + 2639ms (initramfs) + 12732ms (userspace) = 16847ms
I had my host name in /etc/hosts. Interesting the differences in the number of services and the amount of time.
__________________
Registered Linux User #348347
Have you been seduced by siduction? http://siduction.org/index.php
Running Fedora 17/18, siduction and openSUSE Tumbleweed with KDE
|

17th February 2012, 05:00 AM
|
 |
Community Manager
|
|
Join Date: Mar 2004
Location: Vancouver, Canada
Posts: 2,366

|
|
|
Re: How long does systemd take for you?
From the Toshiba AMD E-350 powered laptop (see the sig):
Code:
$ systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
9826ms udev-settle.service
5775ms sendmail.service
3269ms media.mount
3231ms sys-kernel-debug.mount
3206ms sys-kernel-security.mount
3186ms dev-mqueue.mount
3164ms dev-hugepages.mount
3109ms mdmonitor-takeover.service
2846ms var-lib-nfs-rpc_pipefs.mount
2544ms udev-trigger.service
2461ms udev.service
2269ms fedora-loadmodules.service
2123ms remount-rootfs.service
1828ms systemd-remount-api-vfs.service
1256ms firewalld.service
1085ms fedora-storage-init.service
983ms sys-kernel-config.mount
942ms systemd-readahead-replay.service
924ms systemd-readahead-collect.service
911ms fedora-readonly.service
842ms NetworkManager.service
776ms netfs.service
706ms avahi-daemon.service
687ms systemd-vconsole-setup.service
679ms fedora-storage-init-late.service
641ms nfs-lock.service
608ms sm-client.service
536ms rsyslog.service
519ms console-kit-log-system-start.service
456ms rpcbind.service
452ms sandbox.service
441ms iptables.service
440ms systemd-logind.service
430ms ip6tables.service
411ms lvm2-monitor.service
398ms auditd.service
375ms mcelog.service
364ms sshd-keygen.service
348ms systemd-sysctl.service
305ms irqbalance.service
286ms acpid.service
259ms systemd-tmpfiles-setup.service
252ms abrt-ccpp.service
244ms abrt-vmcore.service
203ms dbus.service
126ms boot.mount
116ms home.mount
99ms chronyd.service
89ms console-kit-daemon.service
84ms fedora-wait-storage.service
83ms nfs-idmap.service
23ms systemd-user-sessions.service
21ms rtkit-daemon.service
18ms accounts-daemon.service
0ms sys-fs-fuse-connections.mount
55 services: Total = 67.255 seconds
Code:
$ systemd-analyze time
Startup finished in 1895ms (kernel) + 5685ms (initramfs) + 22028ms (userspace) = 29610ms
__________________
Desktop CPU: AMD Phenom II(tm) X4 Processor 940 AM2+ - Memory: 8GB DDR2-RAM - GPU: Nvidia Geforce GTX 460 v2 - OS: Fedora 18 Spherical Cow x86-64 and Windows 7 Ultimate SP1 64-bit
Laptop Toshiba Satellite C650D - OS: Fedora 19 Schrödinger's Cat (preview release) x86-64 and Microsoft Windows 7 64-bit
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Hybrid Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
Current GMT-time: 14:02 (Monday, 20-05-2013)
|
|
 |
 |
 |
 |
|
|