Graphical boot issues: a.o. graphical boot twice slower then text boot!!!
Dave Jones
davej at redhat.com
Wed Oct 8 11:08:49 UTC 2003
On Tue, Oct 07, 2003 at 07:47:29PM -0400, Owen Taylor wrote:
> This slow down is virtually all in starting up rhgb ... from the
> point where X takes control to the point where rhgb appears on the
> screen is just about 20 seconds; likely this time is mostly spent
> simply reading in libraries from disk, though there are some puzzling
> factors:
>
> - When booting up without rhgb, starting gdm (X => appears on screen)
> takes around 10 seconds. But gdm uses all the libraries that
> rhgb uses and more.
>
> - gdm is no faster to start when rhgb has started before, even though
> many of the libraries that gdm needs should already be in ram.
The restarting of X between rhgb and gdm is a killer on one box I have
with onboard VIA castlerock graphics. When X starts up theres a pause
of around 30 seconds. Seeing this twice per boot makes rebooting that
box really painful. One day when I get time I'll oprofile X and find
out what its doing that takes so long (Unless Mike already knows).
X is obviously doing something wrong there, but additionally, why
can't we reuse the X session we've already started for gdm ?
(Asides from some tricks in gdm startup to make sure we actually did
do a graphical boot, but that shouldn't be too hard).
> B) One of the init steps that runs *after* we start rhgb speeds up
> the system by a large factor. (What? /etc/sysconfig/harddisks
> is run later but does nothing on this test system)
Arjan did a profile of every binary we start up on a typical boot,
that may give you some clues if you take a peek at that..
Dave
--
Dave Jones http://www.codemonkey.org.uk
More information about the fedora-test-list
mailing list