qaz@lemmy.world to Linux@lemmy.mlEnglish · edit-23 anni faTIL You can use systemd-analyze plot > plot.svg to plot the service startup time to find bottleneckslemmy.worldimagemessage-square33linkfedilinkarrow-up1434arrow-down111file-text
arrow-up1423arrow-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 anni famessage-square33linkfedilinkfile-text
minus-squaregermanatlas@lemmy.blahaj.zonelinkfedilinkarrow-up7·3 anni fathe only “bottleneck” i currently have is plymouth-quit-wait.service, which takes 3.9 seconds. i can live with that
minus-squarestifle867@programming.devlinkfedilinkarrow-up7·3 anni faI 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.
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.