Post your boot times

[securitybreach]

Ok, I'll start:

 

On Archlinux (obviously) running a Samsung 840 EVO SSD:

 

comhack@Cerberus ~ % systemd-analyze

Startup finished in 2.296s (kernel) + 886ms (userspace) = 3.183s

 

comhack@Cerberus ~ % systemd-analyze blame

17.083s updatedb.service

7.119s logrotate.service

4.642s man-db.service

1.232s pgl.service

289ms monitorix.service

241ms systemd-modules-load.service

228ms alsa-restore.service

228ms lm_sensors.service

226ms systemd-logind.service

223ms catalyst-hook.service

220ms dev-sda1.device

217ms network.service

216ms cpupower.service

216ms urxvtd@comhack.service

210ms systemd-user-sessions.service

132ms systemd-fsck@dev-disk-by\x2duuid-c30db2b6\x2d90d1\x2d41f1\x2d9d75\x2d6659c0fde970.service

127ms systemd-fsck@dev-disk-by\x2duuid-3067b591\x2d934e\x2d4c73\x2da4a7\x2de5d9da6c267a.service

114ms systemd-fsck@dev-disk-by\x2duuid-cb0d6b0f\x2d1c2a\x2d46c8\x2d99eb\x2dbbe4e1bcb1b5.service

95ms systemd-fsck@dev-disk-by\x2duuid-3fc84665\x2d73ed\x2d46ed\x2da4c6\x2d31d4ce2bc1b7.service

64ms backup2.mount

45ms systemd-fsck@dev-disk-by\x2duuid-7609a908\x2db7a1\x2d4242\x2dab4c\x2d3ee3cc538afb.service

44ms MEDIA.mount

43ms udisks2.service

36ms systemd-udevd.service

34ms Various.mount

32ms colord.service

26ms user@1000.service

25ms systemd-udev-trigger.service

24ms systemd-journald.service

22ms polkit.service

18ms backup.mount

18ms shadow.service

17ms systemd-tmpfiles-setup-dev.service

17ms systemd-vconsole-setup.service

17ms kmod-static-nodes.service

16ms systemd-fsck@dev-disk-by\x2duuid-86a184ad\x2d40b3\x2d46c3\x2db405\x2de7e06fb57ad6.service

16ms systemd-remount-fs.service

15ms systemd-tmpfiles-clean.service

14ms dev-hugepages.mount

 

At one point, I was at a 1.8 second boot but I have added more drives and more services since then.

 

 

These commands only work with systemd but since most distros use systemd, this shouldn't be an issue. That said, I do not know how this is done on sysinit but if anyone knows; feel free to post their boot stats too.

[V.T. Eric Layton]

vtel57@ericsbane06~:$ % systemd-analyze
vtel57@ericsbane06~:$ wtf? -bash: fg: %: no such job

 

[securitybreach]

Well Slackers are behind the times.... Heck even Debian has moved to the dark side

[sunrat]

roger@brain:~$ systemd-analyze

Startup finished in 3.738s (kernel) + 4.535s (userspace) = 8.274s

My system is at least 5 years older than yours, SB. My SSD is OCZ Vertex2 120GB about 4 years old. A bit of system info would help to put it in context.

 

roger@brain:~$ inxi -v 2
System: Host: brain Kernel: 4.0.1-towo.2-siduction-amd64 x86_64 (64 bit) Desktop: KDE 4.14.3
	 Distro: siduction 13.2.0 December - kde - (201312310241)
Machine: Mobo: Gigabyte model: EP45-UD3R v: x.x Bios: Award v: F3 date: 09/18/2008
CPU:	 Dual core Intel Core2 Duo E8500 (-MCP-) speed/max: 2000/3166 MHz
Graphics: Card: NVIDIA GF114 [GeForce GTX 560 Ti]
	 Display Server: X.Org 1.16.4 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1920x1080@59.93hz
	 GLX Renderer: Gallium 0.4 on NVCE GLX Version: 3.0 Mesa 10.4.2
Network: Card: Atheros TP-Link TL-WN821N v3 802.11n [Atheros AR7010+AR9287] driver: ath9k_htc
Drives: HDD Total Size: 3595.7GB (52.4% used) ID-1: model: OCZ
	 ID-2: model: WDC_WD1001FALS ID-3: model: WDC_WD3200KS
	 ID-4: model: Elements_10B8 ID-5: model: MHW2160BH
Info:	 Processes: 181 Uptime: 3 days Memory: 1239.5/3956.9MB Client: Shell (bash) inxi: 2.2.19

[securitybreach]

8 seconds still isn't bad at all. Here is my inxi on this machine:

 

[V.T. Eric Layton]

Well Slackers are behind the times.... Heck even Debian has moved to the dark side

 

Slackers are like cats and old people; they don't like change.

[securitybreach]

Well Slackers are behind the times.... Heck even Debian has moved to the dark side

 

Slackers are like cats and old people; they don't like change.

 

Well we know who to blame for that one.... good ole Pat

[V.T. Eric Layton]

Blame?

 

 

I think you mean "thank."

 

Pat V.

[abarbarian]

$  systemd-analyze
Startup finished in 6.745s (kernel) + 16.193s (userspace) = 22.939s

 

$ inxi -v 2
System:    Host: ************** Kernel: 4.0.1-1-ARCH x86_64 (64 bit)
	   Desktop: WindowMaker 0.95.6  Distro: Arch Linux
Machine:   Mobo: ASUSTeK model: M2N32-SLI DELUXE v: 1.XX
	   Bios: Phoenix v: ASUS M2N32-SLI DELUXE 5002 date: 03/18/2010
CPU:	   Quad core AMD Phenom II X4 965 (-MCP-) speed: 803 MHz (max)
Graphics:  Card-1: NVIDIA GF104 [GeForce GTX 460]
	   Card-2: NVIDIA GF104 [GeForce GTX 460]
	   Display Server: X.Org 1.17.1 driver: nvidia
	   Resolution: 1920x1200, 1920x1080
	   GLX Renderer: GeForce GTX 460/PCIe/SSE2
	   GLX Version: 4.5.0 NVIDIA 349.16
Network:   Card-1: NVIDIA MCP55 Ethernet driver: forcedeth
	   Card-2: NVIDIA MCP55 Ethernet driver: forcedeth
	   Card-3: Realtek RTL8187 Wireless Adapter driver: rtl8187
Drives:    HDD Total Size: 360.1GB (3.0% used) ID-1: model: MKNSSDCR120GB
	   ID-2: model: MKNSSDCR240GB
Info:	  Processes: 112 Uptime: 27 min Memory: 787.4/3956.4MB
	   Client: Shell (bash) inxi: 2.2.19 

 

My problem is the cpu only runs at 800MHz I can run it at 3.4MHz but am not able to govern it, it is a bios problem. I also have done no tweaking of the Arch install so the results show an out of the box install.

I may buy a new mobo and ram to get running at optimum as I have some newer games to play as I am nearly at the end of all the older games I can play at maximum graphics resolution.

 

[securitybreach]

$ systemd-analyze
Startup finished in 6.745s (kernel) + 16.193s (userspace) = 22.939s

 

It is still not that bad at all.

[abarbarian]

$ systemd-analyze
Startup finished in 6.745s (kernel) + 16.193s (userspace) = 22.939s

 

It is still not that bad at all.

 

Yeah it is still quicker than Windows 7 which I run on the same pc.

[burninbush]

I have some questions about this idea of boot times; counting from what? Surely not from flipping the power switch on -- just getting through POST takes 8 - 10 seconds on either of my desktops (quad-core 3ghz AMD II boxes). I have always assumed that was due to the number of partitions on my disks -- 13 total. From hitting Enter at the grub choice takes another 12 - 14 seconds to get to a text login, and then KDE another 15 seconds.

 

Doesn't some large portion of the kernel have to be running to enable system-analyze to even measure times?

 

I have an older SSD here (220 mb/second) that I have also tested with -- it boots faster than the hard disks, but not by much -- IMO, the only parts of bootup where it makes a difference is when the disk light is on, which anybody can see is not nearly the whole bootup process.

 

Any info appreciated.

[securitybreach]

Actually it is measured from the point of hitting enter on your boot manager to your login. The system-analyze is a built in systemd command that is available on any distro running systemd (most all of them now). You can make your bios post a lot faster by changing the option in your bios to silent or whatever your bios calls it. Trust me, I have 6 harddrives in this machine and my post takes less than 2 seconds.

[securitybreach]

You can also use this to tell you which service takes how long and such:

systemd-analyze blame

 

[ comhack@Cerberus ~ % systemd-analyze blame

243ms dev-sda1.device

193ms systemd-modules-load.service

164ms network.service

136ms systemd-fsck@dev-disk-by\x2duuid-c30db2b6\x2d90d1\x2d41f1\x2d9d75\x2d6659c0fde970.servi

115ms systemd-fsck@dev-disk-by\x2duuid-3067b591\x2d934e\x2d4c73\x2da4a7\x2de5d9da6c267a.servi

113ms systemd-fsck@dev-disk-by\x2duuid-cb0d6b0f\x2d1c2a\x2d46c8\x2d99eb\x2dbbe4e1bcb1b5.servi

86ms systemd-fsck@dev-disk-by\x2duuid-3fc84665\x2d73ed\x2d46ed\x2da4c6\x2d31d4ce2bc1b7.servi

86ms monitorix.service

68ms backup2.mount

62ms MEDIA.mount

57ms lm_sensors.service

56ms urxvtd@comhack.service

55ms systemd-logind.service

50ms catalyst-hook.service

48ms systemd-fsck@dev-disk-by\x2duuid-86a184ad\x2d40b3\x2d46c3\x2db405\x2de7e06fb57ad6.servi

46ms udisks2.service

45ms systemd-user-sessions.service

45ms cpupower.service

45ms systemd-fsck@dev-disk-by\x2duuid-7609a908\x2db7a1\x2d4242\x2dab4c\x2d3ee3cc538afb.servi

42ms Various.mount

35ms systemd-udevd.service

34ms systemd-tmpfiles-clean.service

32ms systemd-journald.service

24ms colord.service

21ms polkit.service

20ms systemd-sysctl.service

20ms user@1000.service

19ms systemd-udev-trigger.service

15ms alsa-restore.service

15ms systemd-tmpfiles-setup-dev.service

14ms backup.mount

14ms systemd-vconsole-setup.service

13ms old\x2dhome.mount

12ms tmp.mount

10ms systemd-remount-fs.service

10ms kmod-static-nodes.service

9ms systemd-tmpfiles-setup.service

8ms shadow.service`

[burninbush]

Actually it is measured from the point of hitting enter on your boot manager to your login. The system-analyze is a built in systemd command that is available on any distro running systemd (most all of them now). You can make your bios post a lot faster by changing the option in your bios to silent or whatever your bios calls it. Trust me, I have 6 harddrives in this machine and my post takes less than 2 seconds.

 

 

?? Can you give me a hint where I might find that, or what it is called? Went through every setting on both boxes this morning and except for disable splash screen I see nothing like that. These mobos are about 2 years old.

[securitybreach]

Look for an entry labeled 'power-on self test', 'startup diagnostic', or the like. If you find such an entry, disable it. Alternatively, look for an option called 'Fast Boot' or 'Quick Boot';

[abarbarian]

Actually it is measured from the point of hitting enter on your boot manager to your login. The system-analyze is a built in systemd command that is available on any distro running systemd (most all of them now). You can make your bios post a lot faster by changing the option in your bios to silent or whatever your bios calls it. Trust me, I have 6 harddrives in this machine and my post takes less than 2 seconds.

 

 

?? Can you give me a hint where I might find that, or what it is called? Went through every setting on both boxes this morning and except for disable splash screen I see nothing like that. These mobos are about 2 years old.

 

Which bios are you using ?

 

As Josh says "Quick" boot may be an option an maybe you can turn of any logos that appear or floppy boot seek or kvm if you do not use it or any of the , boot from keyboard/network type stuff, in other words disable or turn of any of the bios stuff you never use.