unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Is it just me, or did 21.3.50 get a whole lot slower?
Date: Sat, 15 Jun 2002 15:47:41 -0600 (MDT)	[thread overview]
Message-ID: <200206152147.g5FLlfU10992@aztec.santafe.edu> (raw)
In-Reply-To: <87adpxob2n.fsf@alice.dynodns.net> (message from John Wiegley on Fri, 14 Jun 2002 13:32:48 -0700)

    First I noticed the nifty new color schemes, and fading modelines.
    However, I also saw that it was WAY WAY slower than 21.2.  'M-x' took
    0.2 seconds to show a prompt; there was a lag on inserting characters;
    RET at the end of a line waiting up to 2 full seconds at time.

Chances are this is due to some rather simple change, and we could
easily fix it if only we knew what.  If it does not happen to most
people, maybe it is due to a change in some package or feature that
you use.  Could you see if it is equally slow if you do `emacs -q'?

Is there any chance you can stop Emacs during those 2 seconds?  If you
can start Emacs under GDB, then during that time if you move the mouse
into the window where GDB is running and type C-c, it might stop
Emacs in time to get a backtrace.  If you do that a few times,
it might show you where the time is being spent.

    What I did notice is lots and lots of screen flicker.  It seems that
    refreshes were happening very often (maybe once every few seconds),
    which is very different from 21.2, where flicker just never happens.

You can set breakpoints in various parts of redisplay, such as
try_window and try_window_id, and set commands on them to continue
automatically.  That way, they will print out in the GDB window but
won't actually stop Emacs.  By comparing the slow version and a faster
version, you might see a difference in pattern which would tell us
something.

  parent reply	other threads:[~2002-06-15 21:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-14 20:32 Is it just me, or did 21.3.50 get a whole lot slower? John Wiegley
2002-06-14 20:55 ` D. Goel
2002-06-15 21:47   ` Richard Stallman
2002-06-16 18:38     ` D. Goel
2002-06-17 16:30       ` Richard Stallman
2002-06-18 16:36         ` D. Goel
2002-06-19  5:17           ` Eli Zaretskii
2002-06-19  6:01             ` John Wiegley
2002-06-19  6:23             ` D. Goel
2002-06-20 14:33           ` Richard Stallman
2002-06-15 17:19 ` Kai Großjohann
2002-06-15 21:47 ` Richard Stallman [this message]
2002-10-19  0:36   ` John Wiegley
2002-12-31  5:48     ` Richard Stallman
2002-12-31  6:12       ` John Wiegley
2003-01-02 18:38         ` Richard Stallman
2003-01-03  5:50           ` John Wiegley
2003-01-03 20:30             ` Richard Stallman
2003-01-04  4:12               ` John Wiegley
2003-01-04 23:54                 ` Kim F. Storm
2003-01-05 18:33                 ` Richard Stallman
2003-01-14 14:40               ` Phillip Lord
2003-01-14 20:12                 ` John Wiegley
2003-01-15 11:05                 ` Richard Stallman
2003-01-15 11:56                   ` Phillip Lord
2003-01-17  9:22                     ` Richard Stallman
2002-11-01  5:21   ` Looks like I found the slowdown John Wiegley
2002-11-02  3:32     ` Richard Stallman

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=200206152147.g5FLlfU10992@aztec.santafe.edu \
    --to=rms@gnu.org \
    --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).