[haiku-bugs] Re: [Haiku] #12258: [launch_daemon] increased boot time
- From: "mmlr" <trac@xxxxxxxxxxxx>
- Date: Sat, 29 Aug 2015 11:39:33 -0000
#12258: [launch_daemon] increased boot time
-------------------------------------+----------------------------
Reporter: diver | Owner: axeld
Type: bug | Status: new
Priority: normal | Milestone: Unscheduled
Component: Servers/launch_daemon | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
-------------------------------------+----------------------------
Comment (by mmlr):
Replying to [comment:25 diver]:
Or even add {{{uptime >> ~/uptime.log}}} at the end of the
UserBootScript.
Yes, very clever, except that "up 0 minutes" doesn't really tell you
much...
As another note: As the launch_daemon starts things in parallel, it
profits from multiple CPUs. When running things in a single CPU VM the
results between pre- and post-launch_daemon should be similar.
I've tested this over here with a gcc2 image before and after the launch
daemon in kvm and the single CPU configuration was the same (10 vs. 10
seconds) while with 4 emulated CPUs (on a quad-core host) the results with
the launch_daemon were better (11 vs. 12 seconds). I attribute the
slowdown with more cores to emulation overhead and slow CPU bootstrap. The
numbers are so similar that it's hard to tell if the launch_daemon helps
things, it certainly doesn't make things drastically worse for me though.
This will likely vary with hardware/emulation software used though.
A possible explanation for the 64 bit builds being quicker (apart from the
better compiler and instruction set) could also be that there just aren't
all drivers present.
--
Ticket URL: <
https://dev.haiku-os.org/ticket/12258#comment:26>
Haiku <
https://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
