Date: Wed, 17 Aug 2022 06:06:41 +0200 From: Ralf Mardorf <ralf-mardorf@riseup.net> To: questions@freebsd.org Subject: Re: How fast can I get FBSD to boot? Message-ID: <b91c20d6f0256607ff2978641078b8bdc75d763a.camel@riseup.net> In-Reply-To: <CAOgwaMsCZM8T=ci5FDAFiBnst5ibxZaMtUPy23%2B380_N=hDH8g@mail.gmail.com> References: <CAHieY7RtGo6j=2bcXT1Xu7iEuz64X0_H%2BL8o=LxH3vz6B2Q4Ww@mail.gmail.com> <CAHieY7S%2BQr7FRVr=nzMhRrPS=xMRNZbtRh4XwteQ99xgFXJX6g@mail.gmail.com> <7cf0e1e9-c531-b7d8-9e0b-e90411e09548@nomadlogic.org> <CAOgwaMsCZM8T=ci5FDAFiBnst5ibxZaMtUPy23%2B380_N=hDH8g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2022-08-17 at 06:15 +0300, Mehmet Erol Sanliturk wrote: > FreeBSD is booting by loading very small parts step by step . >=20 > Linux is booting by loading very large files ( such as 7 MB , 30 MB , > ... ) as boot images to use . This alone doesn't say anything about the speed. A large file of assembled code could be faster, than a small script. A systemd parallel startup could be faster, but might gain absolutely nothing, if parallel starts are impossible, because units might depend on other units and can only be started, after another unit is already running. There is the need to optimise startup, whatever operating system, kernel or init system you are using. Without doubts the fasted way is to start as less as possible assembled code and no script at all. IOW avoiding interpreter based languages, such as shell scripts and only starting/using what is absolutely necessary. The idea of "freezing" the state of a computer and to wake it up when turning on the computer, is also a good way to improve startup speed, but doesn't always work.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b91c20d6f0256607ff2978641078b8bdc75d763a.camel>