you are viewing a single comment's thread
view the rest of the comments
[–] -1 points 1 year ago (6 children)

The big reason I personally dislike Systemd is bloat. It takes me 6 seconds to boot a windows 11 VM, it takes 20+ with Systemd, and it takes 6 seconds with dinit. On real machines I frequently hit 40 seconds with systemd. Now is that enough of a problem that I am going to switch to Windows (ugh) or Chimera/Artix, probably no. I still find it very annoying.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 13 points 1 year ago (5 children)

    That's not normal. Unless you're using an HDD, but then Windows wouldn't boot that fast.

    Check the output of systemd-analyze blame.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 1 year ago* (4 children)

    I have tried. Nothing worked. I also experience the same slow booting on every machine+systemd, with the same resulting slow boot up. Even friends have mentioned to me the slow boot times compared to Windows.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 5 points 1 year ago (3 children)

    I boot to login in probably under 5 seconds, so 30+ seconds seems like something is not configured correctly. And every Windows machine I've ever interacted with boots slow and updates even slower.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 1 year ago* (2 children)

    Idk what is wrong but every fresh install on any Systemd distro (Arch, Fedora, Debian, openSUSE) has the same slow boot on every device I have tried. I have never seen a 5 second boot on anything else but dinit.

    Oh, and my disk is a modern M.2 SSD for my workstation.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 year ago (1 child)

    I did a fresh install of fedora in a VM given 4 cores, 16gb ram, and storage on an NVME SSD. Finally I am getting a reasonable boot time of 6.5 seconds. But on bare metal I can't get anywhere close to that. Firmware alone takes 15 seconds. Either way, now I know that it isn't a "Systemd problem", just that only Systemd gives me this problem.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 1 year ago* (last edited 1 year ago)

    If you actually want to fuss with it you could always try some of the stuff from the Holy Wiki and see if it makes a difference. Sometimes it's just "gremlins" though.

    I ironically had a similar issue with moving to Wayland from X. I did everything I saw documented to make it work and it just either flat out didn't, or performance was ass. Then I think when I had read about Gnome's future plans to drop X I figured I needed to give it another go. In the end I'm not sure what made the difference (update/config/etc.), but I'm using Wayland now and performance seems the same/better and all is good. My install is also probably close to a decade old (or more - I have moved it between at least 3 disks) at this point so I also have cruft out the ass lol.

    Edit - Got curious and decided to look and this install is dated 2013-02-24, so longer than I thought.

  • source
  • parent