From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: dmoncayo@gmail.com, emacs-devel@gnu.org
Subject: Re: Two strange messages while building Emacs on MS-Windows
Date: Mon, 10 Dec 2012 11:59:14 +0200 [thread overview]
Message-ID: <83pq2ib53h.fsf@gnu.org> (raw)
In-Reply-To: <jwvzk1nb53u.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Sun, 09 Dec 2012 10:50:31 -0500
> Cc: emacs-devel@gnu.org, dmoncayo@gmail.com
>
> I do "make -j2" and get about %170 of cpu utilisation (most of the
> less-than-100% is due to phases in the build process where we only have
> one process running, such as when running `configure'), so presumably my
> 6min would turn into no more than 10min if run sequentially.
FWIW, "make -j2 bootstrap" was timed as follows:
real 17m2.832s
user 23m4.760s
sys 4m45.010s
on this machine:
Linux fencepost.gnu.org 2.6.32-42-server #1trisquel3 SMP Sat Aug 11 18:02:12 UTC 2012 x86_64 GNU/Linux
whose /proc/cpuinfo says, inter alia:
vendor_id : AuthenticAMD
cpu family : 16
model : 9
model name : AMD Opteron(tm) Processor 6128
stepping : 1
cpu MHz : 2000.078
cache size : 512 KB
This machine was 98% idle when I timed the bootstrap.
This command:
time emacs --batch --eval '(message "Hello")'
(with an unoptimized build of Emacs) takes between 0.085s and 0.123s
on this machine. (Why this is 5 times slower than Óscar's slower
machine is also unclear.)
The command "cd lisp && make compile-always", which sequentially
compiles every Lisp file, was timed on this machine as follows:
real 23m11.277s
user 16m50.820s
sys 2m45.910s
The same command with "make -j2" times like this:
real 11m51.381s
user 17m15.850s
sys 2m49.410s
which is an entirely reasonable 2-fold speedup in the elapsed time
(and seems to reveal some bug in accounting for user- and
system-times).
According to http://www.cpubenchmark.net, the CPU marks of the
machines mentioned in this thread are, top to bottom:
Intel Core i7-2600 8,628
AMD Opteron 6128 4,999
Intel Core i5-2410M 3,186
Intel Core2 Quad Q6600 2,941
Intel Core 2 duo T9300 1,709
So I have no idea how Stefan gets a 6-min bootstrap on his 2.5-GHz
T9300 Core 2 duo... Probably missing some factor here. I thought
maybe the filesystem used on fencepost could be it, but "df -hT ."
there says:
Filesystem Type Size Used Avail Use% Mounted on
/dev/xvdb1 ext4 493G 378G 115G 77% /srv/data
and my, perhaps incorrect, reading of that is that this is a local
ext4 filesystem.
next prev parent reply other threads:[~2012-12-10 9:59 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
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 [this message]
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=83pq2ib53h.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).