On 29/04/14 07:34 PM, Toyam Cox wrote: > On Tue, Apr 29, 2014 at 7:20 PM, Simon Brand > <simon.brand@xxxxxxxxxxxxxxxx>wrote: > >> >> >> Am 30.04.2014 00:06, schrieb Toyam Cox: >>> NetworkManager.service is running for 12 seconds >> >> Can you use static ip address in your network? >> The dhcp client did eat a lot of time here, too. >> 9 sec boot here without cryptsetup and static ip. >> Server needs 20 sec without ssd, 15 sec for dhcpcd, mysql and php-fpm >> >> > I do not believe that would help, because often I start up in areas without > a network. Perhaps there is a way to get Network Manager to start after the > boot is completed, or at least not be a boot dependency? NetworkManager works fine with roaming and can be configured to use a static IP on some networks but not others. I don't see what you have to gain by removing it from the regular boot process... just make sure you're not letting stuff block on it. This is with NetworkManager enabled on a wireless network with a Samsung 840 EVO (it varies from ~2-3s for kernel + userspace): Startup finished in 3.070s (firmware) + 60ms (loader) + 1.655s (kernel) + 676ms (userspace) 160ms NetworkManager.service AFAIK it doesn't count the time needed to connect over DHCP... it's often not connected by the time I have a browser and a few terminals open in i3 since it takes 10 seconds. Not that boot time should matter to anyone, since kernel upgrades aren't every day and there's not much reason to reboot otherwise :P.
Attachment:
signature.asc
Description: OpenPGP digital signature
