Apparently the reason my computer has been taking 2 minutes to boot was a faulty network mount

  • jsdz@lemmy.ml
    108·
    2 years ago

    I’m pretty sure the main system startup bottleneck is me typing the disk encryption passphrase.

    • stifle867@programming.dev
      19·
      2 years ago

      The top/1st line is the first service and it cascaded down as each subsequent service starts. Left to right is time elapsed. Bright red line is time to start that service. Shorter is better.

      Does that help?

    • qaz@lemmy.worldOP
      4·
      2 years ago

      No, there currently isn’t

      And it’s not as easy to add actually. Note that systemd only keeps units loaded as long as they are referenced by something else that is loaded, are running, have failed, or have a job queued. That means if a service is terminated at shutdown there’s a very good chance it is GC’ed away pretty quickly. Now, while systemd keeps timestamping info around for services that tell us how long a service was running, took to start or took to shut down all that info is lost the instant the unit is GC’ed away…

      Source

    • qaz@lemmy.worldOP
      41·
      2 years ago

      Thanks for the article, I’ve already spotted a few utilities that can come in useful. I’ve heard a lot of criticism about systemd too, but never really actively used it myself until a few weeks ago. I actually quite like it from what I’ve seen so far.

  • gayhitler420@lemm.ee
    201·
    2 years ago

    I wrote a long-ish comment in another thread explaining why lots of people don’t like systemd.

    Stuff like this is why people do like systemd.

    The massive, un unixy and complex tools allow for very powerful and somewhat knowledge agnostic approaches to all sorts of problems.

    One of the nicest things about systemds toolset is that it allows a person who relies on finding the problem and googling it to resolve thing much faster than their alternative, learn what’s going on and figure it out.

    I don’t mean that as a pejorative, plenty of computer work is maintenance as opposed to engineering and there’s nothing wrong with that.

  • miss_brainfart@lemmy.ml
    11·
    2 years ago

    It tells me that my system boots in 7 seconds. That’s pretty cool, considering that it’s installed on a plain old sata SSD.

    POST, however…

  • germanatlas@lemmy.blahaj.zone
    111·
    2 years ago

    the only “bottleneck” i currently have is plymouth-quit-wait.service, which takes 3.9 seconds. i can live with that

    • stifle867@programming.dev
      9·
      2 years ago

      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.

  • droidpenguin@lemmy.world
    9·
    2 years ago

    Dang had no idea this was a thing, but this looks very useful! I’ve been meaning to troubleshoot slow startup on one of my servers.

  • lntl@lemmy.ml
    61·
    2 years ago

    this is interesting! if i had a two minute boot time, I’d look for ways to figure out what’s going on.

    i remember init messages used to be printed to the console, but nowadays all i get is Manjaro branding. anyone know how to get my console messages back from systemd?

  • bc3114@lemmy.ml
    4·
    2 years ago

    Aha! Reminds me of the good old days when I tried to minimize boot up time on my puny Ivy Bridge i5 laptop. Those days were fun!