From: James Cloos <cloos@jhcloos.com>
To: emacs-devel@gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>, Richard Stallman <rms@gnu.org>,
Miles Bader <miles@gnu.org>
Subject: Re: 15 seconds to fontify index
Date: Tue, 03 Apr 2007 12:33:38 -0400 [thread overview]
Message-ID: <m3wt0tju2u.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <87abxqz8fx.fsf@catnip.gol.com> (Miles Bader's message of "Tue\, 03 Apr 2007 08\:02\:26 +0900")
>>>>> "Miles" == Miles Bader <miles@gnu.org> writes:
Miles> $ time emacs -Q -nw --eval '(info "(elisp)Index")' -kill
I tried that a couple of times in a row on my 1GHz P3M laptop.
With a cold cache it took:
real 0m11.614s
user 0m2.568s
sys 0m0.205s
but with a hot cache that drops down to:
real 0m2.794s
user 0m2.542s
sys 0m0.157s
So it seems a huge part of it is io wait.
NB that my info dir is compressed, so that time includes gunzip(1) time.
In doing this test, I discovered that my latest updates did not remove
the old copies of the emacs and elisp info pages. The latest installs
I have (by way of the Gentoo ebuild) use bzip2(1) rather than gzip(1)
to compress the files. Removing the old, thus forcing the new, bumps
the time up to just under 10 seconds of user time, or about 3.83 times
as long.
So, perhaps part of the slowdown is that distributors are compressing
the info pages. Especially if with bzip2(1).
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next prev parent reply other threads:[~2007-04-03 16:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 21:42 15 seconds to fontify index Richard Stallman
2007-04-01 21:57 ` Nick Roberts
2007-04-02 4:30 ` Chong Yidong
2007-04-02 12:23 ` Eli Zaretskii
2007-04-02 12:33 ` David Kastrup
2007-04-02 13:00 ` Eli Zaretskii
2007-04-03 10:41 ` Yavor Doganov
2007-04-01 22:04 ` Alan Mackenzie
2007-04-01 22:41 ` Andreas Schwab
2007-04-02 0:58 ` Stefan Monnier
2007-04-02 12:17 ` Eli Zaretskii
2007-04-02 18:05 ` Reiner Steib
2007-04-02 23:02 ` Miles Bader
2007-04-03 16:33 ` James Cloos [this message]
2007-04-03 23:40 ` Miles Bader
2007-04-04 14:02 ` Richard Stallman
2007-04-03 7:46 ` Richard Stallman
2007-04-03 0:04 ` Kevin Ryde
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=m3wt0tju2u.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=rms@gnu.org \
/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).