From: Eli Zaretskii <eliz@gnu.org>
To: dmoncayo@gmail.com
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Two strange messages while building Emacs on MS-Windows
Date: Wed, 12 Dec 2012 20:41:26 +0200 [thread overview]
Message-ID: <836247865l.fsf@gnu.org> (raw)
In-Reply-To: <83obi07wws.fsf@gnu.org>
> Date: Wed, 12 Dec 2012 05:48:51 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
>
> > Date: Tue, 11 Dec 2012 22:58:33 +0100
> > From: Dani Moncayo <dmoncayo@gmail.com>
> > Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
> >
> > > As expected. So, if compiling the C sources takes 1 min and compiling
> > > the Lisp files takes 6.5 min, how come the bootstrap takes 15 min?
> > > What else takes 7.5 min?
> >
> > I don't know. It seems that a bootstrap is not equivalent to the sum
> > of the two commands we've measured.
>
> The only other thing is deleting files at the beginning of bootstrap.
>
> I suggest to bootstrap with a clock in your hand, and make notes about
> the times each part takes. There are at least 5 min more to gain
> here, so I think you should be motivated enough ;-)
This is a bit longish message, sorry. The bottom line is that I think
I know where those 5 min come from, and that Dani should get used to
the 15-min mark for the time being.
First, on my Core i7 running XP, and with "make -j8", the detailed
time schedule of a full bootstrap are:
1:10 min for the initial compilation of C sources
0:30 min for generating loaddefs
4:10 min for compiling Lisp files
0:26 min for the final compilation of C sources
6:46 min total
After the bootstrap, removing all the *.elc files and recompiling them
with emacs.exe, which includes a byte-compiled byte compiler, takes
about 2:30 to 3 min with "make -j8", which is 60% of the time it takes
using an interpreted byte compiler. Not the 25% I somehow measured a
day or two ago.
I also did measurements on a Windows 7 machine. This one has a Core 2
duo E7300 CPU, so it is slightly less powerful than what Dani has.
Here's the bootstrap schedule on that machine using "make -j2":
1:45 min for the initial compilation of C sources
0:50 min for generating loaddefs
11:35 min for compiling Lisp files
0:50 min for the final compilation of C sources
16:00 min total
Removing *.elc files and recompiling all of them with byte-compiled
compiler and "make -j2" takes 6:00 minutes, which is again almost
twice faster. IOW, the missing 5 min are the difference between
compiling Lisp files with an interpreted byte compiler and a
byte-compiled one.
So I guess the 15 min that Dani gets is what is possible on a 2-core
machine, and any further improvements are possible only if Emacs is
re-dumped with byte-compiled preloaded filed early on and then that
binary used to compile the rest of Lisp files, like we do on Unix.
next prev parent reply other threads:[~2012-12-12 18:41 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 19:21 Two strange messages while building Emacs on MS-Windows Dani Moncayo
2012-12-07 19:54 ` Glenn Morris
2012-12-07 19:57 ` Glenn Morris
2012-12-07 20:17 ` Dani Moncayo
2012-12-07 21:35 ` Eli Zaretskii
2012-12-07 22:11 ` Dani Moncayo
2012-12-07 22:35 ` Stefan Monnier
2012-12-08 8:02 ` Eli Zaretskii
2012-12-08 8:43 ` Dani Moncayo
2012-12-08 9:24 ` Eli Zaretskii
2012-12-08 23:06 ` Stefan Monnier
2012-12-09 3:44 ` Eli Zaretskii
2012-12-09 15:50 ` Stefan Monnier
2012-12-09 18:15 ` Óscar Fuentes
2012-12-09 18:52 ` Eli Zaretskii
2012-12-09 19:31 ` Óscar Fuentes
2012-12-09 22:14 ` Eli Zaretskii
2012-12-09 22:44 ` Óscar Fuentes
2012-12-10 6:06 ` Eli Zaretskii
2012-12-10 11:11 ` Óscar Fuentes
2012-12-10 14:37 ` Eli Zaretskii
2012-12-10 15:42 ` Óscar Fuentes
2012-12-10 16:20 ` Eli Zaretskii
2012-12-09 22:00 ` Eli Zaretskii
2012-12-09 23:31 ` Dani Moncayo
2012-12-10 6:13 ` Eli Zaretskii
2012-12-10 20:57 ` Dani Moncayo
2012-12-10 21:08 ` Eli Zaretskii
2012-12-10 21:33 ` Dani Moncayo
2012-12-11 6:49 ` Eli Zaretskii
2012-12-11 7:18 ` Dani Moncayo
2012-12-11 7:51 ` Eli Zaretskii
2012-12-11 20:41 ` Dani Moncayo
2012-12-11 21:00 ` Eli Zaretskii
2012-12-11 20:41 ` Dani Moncayo
2012-12-11 21:05 ` Eli Zaretskii
2012-12-11 21:58 ` Dani Moncayo
2012-12-11 22:55 ` Stefan Monnier
2012-12-12 3:50 ` Eli Zaretskii
2012-12-12 14:26 ` Stefan Monnier
2012-12-12 17:18 ` Eli Zaretskii
2012-12-12 18:42 ` Eli Zaretskii
2012-12-12 3:48 ` Eli Zaretskii
2012-12-12 18:41 ` Eli Zaretskii [this message]
2012-12-11 7:57 ` Daniel Colascione
2012-12-11 20:42 ` Dani Moncayo
2012-12-11 20:47 ` Daniel Colascione
2012-12-11 20:58 ` Dani Moncayo
2012-12-11 20:59 ` Daniel Colascione
2012-12-11 21:01 ` Dani Moncayo
2012-12-11 21:02 ` Daniel Colascione
2012-12-10 9:59 ` Eli Zaretskii
2012-12-10 10:37 ` Romain Francoise
2012-12-10 14:42 ` Eli Zaretskii
2012-12-10 15:33 ` Romain Francoise
2012-12-10 16:04 ` Eli Zaretskii
2012-12-10 14:44 ` Eli Zaretskii
2012-12-07 22:57 ` joakim
2012-12-08 8:08 ` Eli Zaretskii
2012-12-08 10:58 ` joakim
2012-12-08 11:35 ` Óscar Fuentes
2012-12-08 12:12 ` Óscar Fuentes
2012-12-08 12:44 ` Eli Zaretskii
2012-12-08 13:24 ` Óscar Fuentes
2012-12-08 13:38 ` Eli Zaretskii
2012-12-09 1:18 ` Óscar Fuentes
2012-12-08 12:33 ` Eli Zaretskii
2012-12-07 21:35 ` Stefan Monnier
2012-12-09 3:20 ` Jason Rumney
2012-12-07 20:17 ` Dani Moncayo
2012-12-07 21:24 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=836247865l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dmoncayo@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).