Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

i am quite new to Linux, and recently i happily install fedora 16 on my Acer laptop, it was wonderful in the beginning, but now the startup becomes very lagging. i Google it and run the command systemd-analyze blame, the result is below:

11454ms fedora-loadmodules.service   
8697ms fedora-readonly.service      
6334ms fedora-wait-storage.service   
3740ms systemd-binfmt.service      
3407ms systemd-vconsole-setup.service   
3191ms fedora-storage-init.service   
2956ms udev-settle.service   
2812ms media.mount   
2750ms dev-mqueue.mount   
2728ms dev-hugepages.mount     
2715ms remount-rootfs.service   
2714ms sys-kernel-security.mount      
2698ms sys-kernel-debug.mount   
2348ms proc-sys-fs-binfmt_misc.mount     
2317ms udev-trigger.service   
2301ms udev.service   
1838ms sys-kernel-config.mount   
1598ms mdmonitor-takeover.service   
1490ms systemd-remount-api-vfs.service    
841ms systemd-sysctl.service       
560ms NetworkManager.service    
537ms fedora-storage-init-late.service   
403ms rsyslog.service    
393ms chronyd.service    
378ms console-kit-log-system-start.service       
360ms avahi-daemon.service    
329ms iptables.service    
328ms ip6tables.service    
305ms systemd-readahead-collect.service    
304ms mcelog.service    
300ms auditd.service    
280ms abrt-vmcore.service   

..... etc....

As an average user (who normally just surf internet and read emails), how should i optimize my startup services to speed up my booting time?

share|improve this question

migrated from May 11 '12 at 2:53

This question came from our site for professional and enthusiast programmers.

The blame command only says how long each process took, it doesn't show what the overall timing was. There are two things to look at, first grep systemd /var/log/syslog and it should provide the overall time. Also do systemd-analyze plot > plot.svg && eog plot.svg to get a pretty graph showing the sequence. systemd does a lot in parallel so this should help isolate what is waiting for what. – Paul May 11 '12 at 6:04
Wow!Thanks. the 'grep systemd /var/log/syslog' doesn't work, say no such file, i try 'grep systemd /var/log/boot.log' instead, the output is below: systemd-fsck[961]: /dev/sda3: clean, 231/128016 files, 76693/512000 blocks (check in 5 mounts) systemd-fsck[981]: /dev/mapper/VolGroup-lv_home: clean, 15033/9216000 files, 1732633/36839424 blocks then i run 'systemd-analyze plot > plot.svg && eog plot.svg', the graph is nice, and i found fedora-storage-init.service and fedora-readonly.service takes a long red bar. how should i improve them? – Bob Cao May 11 '12 at 18:40

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.