The memory usage is as Systemd has lots of daemons and services running the background. The CPU usage uplift is mainly during boot, as Systemd is sorting itself out.
I see ! Is this a concrete issue, as in does your system stall easily ? or is it more ideological ? Sometimes it’s difficult to make sense of that as a layman
It’s really a non-issue, on modern CPUs (Multiple cores, 3+GHz) with modern amounts of memory (8 - 32+GB) it’s barely noticeable. I’ve never heard of Systemd causing the computer to stall and most users will never even be aware of the relatively high memory consumption.
The biggest flaw with Systemd is violating the Unix philosphy, Systemd does multiple things for example. The only people who are going to actively hunt down things like Artix probably have used / use Gentoo or Arch (I use Arch btw) and running a very minimal install. I’d be flabbergasted if any mainstream distro like Ubuntu replaces Systemd (Knowing Cannonical it’ll be a Snap-packaged init system lol).
The memory usage is as Systemd has lots of daemons and services running the background. The CPU usage uplift is mainly during boot, as Systemd is sorting itself out.
I see ! Is this a concrete issue, as in does your system stall easily ? or is it more ideological ? Sometimes it’s difficult to make sense of that as a layman
It’s really a non-issue, on modern CPUs (Multiple cores, 3+GHz) with modern amounts of memory (8 - 32+GB) it’s barely noticeable. I’ve never heard of Systemd causing the computer to stall and most users will never even be aware of the relatively high memory consumption.
The biggest flaw with Systemd is violating the Unix philosphy, Systemd does multiple things for example. The only people who are going to actively hunt down things like Artix probably have used / use Gentoo or Arch (I use Arch btw) and running a very minimal install. I’d be flabbergasted if any mainstream distro like Ubuntu replaces Systemd (Knowing Cannonical it’ll be a Snap-packaged init system lol).
Thanks for clarifying
No problem :)