qaz@lemmy.world to Linux@lemmy.mlEnglish · edit-29 months agoTIL You can use systemd-analyze plot > plot.svg to plot the service startup time to find bottleneckslemmy.worldimagemessage-square62fedilinkarrow-up1792arrow-down116file-text
arrow-up1776arrow-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-29 months agomessage-square62fedilinkfile-text
minus-squaregermanatlas@lemmy.blahaj.zonelinkfedilinkarrow-up15arrow-down1·9 months 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-up11·9 months 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-up7·9 months 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