On Wednesday, September 2, 2020 6:09:26 AM MST Zbigniew Jędrzejewski-Szmek
On Sat, Aug 29, 2020 at 09:27:33PM -0600, Chris Murphy wrote:
> These are based on Fedora-Workstation-Live-x86_64-33-20200828.n.0.iso
> in a VM. The numbers are different on bare metal but correlate.
> The only standout is rngd.service. That's a pretty big single hit,
> percentage wise. And I don't know if we even need it anymore. Among
> the rest, perhaps atd.service and crond.service could be disabled by
> default on new installations, in favor of systemd timers.
I think that with the recent-ish kernel changes to make /dev/urandom
non-blocking, rngd should not be installed by default.
As for crond and atd, I think we can keep them installed by default,
but inactive. I.e. make them socket activated or path activated, so that
they are only started if people install actual crontabs or run at.
Instead, why not just have these start in the background, so that they don't
inhibit the start of `sddm` or `lightdm`?
We would also need to convert any packaged cronfiles into systemd
timers. But it seems that this is already mostly done. On my machine,
/etc/cron.weekly/98-zfs-fuse-scrub is the only real crontab entry.
Those are not big programs, but each thing that is running on a
machine has some small impact...
Having these start in the background would remove that startup impact.
John M. Harris, Jr.