From: Robert <Robert.Folland@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: 22.2 slower than 21.3
Date: Mon, 1 Sep 2008 01:14:03 -0700 (PDT) [thread overview]
Message-ID: <046c5ebb-a045-4b0b-9020-436452d80158@l64g2000hse.googlegroups.com> (raw)
In-Reply-To: mailman.17893.1220019825.18990.help-gnu-emacs@gnu.org
Hi Alan!
On Aug 29, 4:27 pm, Alan Mackenzie <a...@muc.de> wrote:
> Hi, Robert!
>
> On Fri, Aug 29, 2008 at 01:06:52AM -0700, Robert wrote:
> > Hi,
> > I just installed 22.2 (pre-built binary for Windows XP), but find it
> > slower than 21.3. I notice when opening C-files. I went straight back
> > to 21.3 now because of that.
>
> There was a bug in older CC Modes which made it "necessary" to scan
> entire buffers when loading them. It was this:
OK, didn't know there was a new CC-mode.
> > Will this get faster in upcoming versions? The problem could perhaps
> > also be that the binary for Windows was built differently. Have
> > others seen the same as me?
>
> Could you give me some figures, please? _HOW_ much slower is the new CC
> mode? Could you please do:
> (i) C-x C-f for a large C file please, one stored on your local hard
> drive. Then kill the buffer with C-x k, thus ensuring the file is in
> the file system cache, if any.
> (ii) Do C-x C-f for this file again, and say how long it takes.
> (iii) Do C-x C-f for the same file in Emacs 21.x. How long does this
> take?
> (iv) State how large the file is, and what make and speed of CPU you
> have.
I only loaded a file of 518k, a C-file of about 10000 lines. I tried
now and it takes about 5 seconds to load in 22.2, actually 6 seconds
if I don't use reverse video (which I normally use). The 22.2.91
version takes less than 1 second.
> If there is a real problem here, like files taking 1 minute to load,
> it'll get fixed. If it's a case of the loading feeling a bit sluggish
> (an extra 1 or 2 seconds to load), it may be possible to optimise things
> a bit.
OK, so this is only a few seconds difference. Now I concatenated the
file I had to get a larger C-file of 2 MB:
2.22: 17 seconds
2.22.91: 0.8 seconds
I loaded the file first, then killed the buffer and then I timed the
loading.
With 2.22.91 I get another problem though, with SLIME:
---
An error has occurred while loading `e:/home/rfo/.emacs':
Wrong number of arguments: (lambda (&optional contribs) Setup Emacs so
that lisp-mode buffers always use SLIME.
CONTRIBS is a list of contrib packages to load. (when (member (quote
lisp-mode) slime-lisp-modes) (add-hook (quote lisp-mode-hook) (quote
slime-lisp-mode-hook))) (when contribs (add-to-list (quote load-path)
(expand-file-name contrib slime-path)) (dolist (c contribs) (require
c) (let ((init (intern (format %s-init c)))) (when (fboundp init)
(funcall init)))))), 2
---
This does not happen in 21.3 or 22.2.
Regards,
-Robert
next prev parent reply other threads:[~2008-09-01 8:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 8:06 22.2 slower than 21.3 Robert
2008-08-29 11:22 ` Martin Fischer
2008-08-29 11:35 ` Robert
2008-08-29 14:27 ` Alan Mackenzie
[not found] ` <mailman.17893.1220019825.18990.help-gnu-emacs@gnu.org>
2008-09-01 8:14 ` Robert [this message]
2008-09-01 8:47 ` Robert
2008-09-14 21:52 ` David Combs
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=046c5ebb-a045-4b0b-9020-436452d80158@l64g2000hse.googlegroups.com \
--to=robert.folland@gmail.com \
--cc=help-gnu-emacs@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.
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).