unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard M Stallman <rms@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: bug-cc-mode@gnu.org, acm@muc.de, davemilter@gmail.com,
	emacs-devel@gnu.org
Subject: Re: open large file with C code: is it realy should be so slow?
Date: Thu, 08 Jan 2009 06:37:52 -0500	[thread overview]
Message-ID: <E1LKtCy-0005P8-JD@fencepost.gnu.org> (raw)
In-Reply-To: <87aba3kj99.fsf@cyd.mit.edu> (message from Chong Yidong on Tue, 06 Jan 2009 20:16:50 -0500)

    Apparently, the netbook you are using (Lemote Yeeloong) has a 600-800
    MHz processor.  That shouldn't be so slow as to yield 20 second loading
    times.  There's likely something strange going on.  Could you try with
    Emacs 22 and see if the problem recurs there?

Visiting the small .c file below takes around 2 seconds in Emacs 22.
It takes 15 or 20 seconds in Emacs 23.  In both cases I used -Q
and visited the file first thing after Emacs started.

char *p = 0;

main ()
{
  *p = 1;
}




  reply	other threads:[~2009-01-08 11:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01 10:01 open large file with C code: is it realy should be so slow? Dave Milter
2008-12-01 12:37 ` Alan Mackenzie
2009-01-04 22:07   ` Dave Milter
2009-01-04 23:31     ` Alan Mackenzie
2009-11-01 17:01       ` Dave Milter
2009-01-06  0:01     ` Richard M Stallman
2009-01-06  5:52       ` Chong Yidong
2009-01-06 22:59         ` Richard M Stallman
2009-01-07  1:16           ` Chong Yidong
2009-01-08 11:37             ` Richard M Stallman [this message]
2009-01-08 12:42               ` Alan Mackenzie
2009-01-06 19:03       ` Alan Mackenzie
2009-01-06 21:50         ` Stefan Monnier
2009-12-04 15:25     ` Alan Mackenzie
2009-12-19 10:51       ` Dave Milter
2009-12-27 10:33         ` Dave Milter

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=E1LKtCy-0005P8-JD@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=acm@muc.de \
    --cc=bug-cc-mode@gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=davemilter@gmail.com \
    --cc=emacs-devel@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).