Re: Release update

[Eli Zaretskii]

> From: "Drew Adams" <address@hidden>
> Date: Mon, 22 Dec 2008 15:04:05 -0800
> Cc: address@hidden
> 
> Another noticeable problem is the time it takes Emacs to start up. I know that
> people have tried to improve this, but for me this startup time has not 
> changed,
> as of this build:
> 
> In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
>  of 2008-12-19 on LENNART-69DE564
> Windowing system distributor `Microsoft Corp.', version 5.1.2600
> configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/g/include
> -fno-crossjumping'
> 
> Whether I use my own setup of a standalone minibuffer frame and one other,
> principal frame or I use emacs -Q, the startup time is about the same. And
> that's true whether I start by editing a file or Dired or just start with
> *scratch*.
> 
> With my own setup, it takes on average 15-20 seconds for the initial frame to
> appear, and another 10 seconds for my two-frame setup to finish. emacs -Q 
> takes
> 15-20 seconds on average for the frame to appear. The command I use is this:
> runemacs.exe -Q --debug-init. This is on a 1-year-old laptop with 2G RAM and
> pretty good processors.
> 
> The startup time is variable, for some reason. Sometimes it is much less (as 
> if
> something were cached), sometimes it is a little more. Usually it is about 
> 15-20
> sec.

Does the disk LED flicker considerably during the long startups?