On Saturday, August 29, 2020 8:27:33 PM MST Chris Murphy wrote: > Hi, > > 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. > > Startup finished in 1.320s (kernel) + 1.344s (initrd) + 7.727s > (userspace) = 10.392s > disable atd.service > Startup finished in 1.308s (kernel) + 1.310s (initrd) + 7.557s > (userspace) = 10.176s > disable dbxtool.service > Startup finished in 1.302s (kernel) + 1.291s (initrd) + 7.527s > (userspace) = 10.120s > disable import-state.service > Startup finished in 1.308s (kernel) + 1.326s (initrd) + 7.410s > (userspace) = 10.044s > disable iscsi.service > Startup finished in 1.316s (kernel) + 1.303s (initrd) + 7.177s > (userspace) = 9.797s > disable libvirtd.service > Startup finished in 1.316s (kernel) + 1.266s (initrd) + 6.779s > (userspace) = 9.361s > disable lvm2-monitor.service > Startup finished in 1.315s (kernel) + 1.323s (initrd) + 6.750s > (userspace) = 9.389s > disable mdmonitor.service > Startup finished in 1.316s (kernel) + 1.350s (initrd) + 6.675s > (userspace) = 9.342s > disable ModemManager.service > Startup finished in 1.270s (kernel) + 1.305s (initrd) + 7.052s > (userspace) = 9.629s > disable nfs-convert.service > Startup finished in 1.312s (kernel) + 1.343s (initrd) + 6.958s > (userspace) = 9.614s > disable rngd.service > Startup finished in 1.308s (kernel) + 1.277s (initrd) + 5.247s > (userspace) = 7.833s > disable switcheroo-control.service > Startup finished in 1.308s (kernel) + 1.334s (initrd) + 5.223s > (userspace) = 7.867s > disable vboxservice.service > Startup finished in 1.301s (kernel) + 1.302s (initrd) + 5.176s > (userspace) = 7.780s > disable crond.service > Startup finished in 1.310s (kernel) + 1.278s (initrd) + 5.076s > (userspace) = 7.665s > > preset-all > Startup finished in 1.316s (kernel) + 1.312s (initrd) + 7.869s > (userspace) = 10.498s ##stopwatch 11.35 > disable atd.service crond.service iscsi.service rngd.service > vboxservice.service > Startup finished in 1.305s (kernel) + 1.294s (initrd) > + 5.505s > (userspace) = 8.105s ##stopwatch 8.89 > > All of these times are based on 'systemd-analyze'. The stopwatch > method is less precise but still demonstrates the difference is real. > > It may not be a big enough deal to do anything about it this cycle, > but could be something to look at for the next. Maybe more > opportunities are available. Unless systemd timers run crontab entries, crond and atd cannot be disabled. Instead, perhaps these could be marked such that they'll start in the background, instead of inhibiting the sddm/whatever GNOME's service is from starting, if they're not already marked as such. -- John M. Harris, Jr. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
