qaz@lemmy.world to Linux@lemmy.mlEnglish · edit-23 years agoTIL You can use systemd-analyze plot > plot.svg to plot the service startup time to find bottleneckslemmy.worldimagemessage-square32linkfedilinkarrow-up1570arrow-down115file-text
arrow-up1555arrow-down1imageTIL You can use systemd-analyze plot > plot.svg to plot the service startup time to find bottleneckslemmy.worldqaz@lemmy.world to Linux@lemmy.mlEnglish · edit-23 years agomessage-square32linkfedilinkfile-text
minus-squaregermanatlas@lemmy.blahaj.zonelinkfedilinkarrow-up11arrow-down1·3 years agothe only “bottleneck” i currently have is plymouth-quit-wait.service, which takes 3.9 seconds. i can live with that
minus-squarestifle867@programming.devlinkfedilinkarrow-up9·3 years agoI know you put bottleneck is quotes but just to explain… apparently this service is simply the splash screen that waits on a ready environment. It doesn’t actually delay anything.
minus-squareSwedneck@discuss.tchncs.delinkfedilinkarrow-up5·3 years agoabrtd.service, 34 seconds… thanks fedora, very cool
the only “bottleneck” i currently have is plymouth-quit-wait.service, which takes 3.9 seconds. i can live with that
I know you put bottleneck is quotes but just to explain… apparently this service is simply the splash screen that waits on a ready environment. It doesn’t actually delay anything.
abrtd.service, 34 seconds…
thanks fedora, very cool