unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs Slowdown
Date: Tue, 10 Mar 2015 21:00:42 +0200	[thread overview]
Message-ID: <8361a865k5.fsf@gnu.org> (raw)
In-Reply-To: <87wq2pf2pw.fsf@newcastle.ac.uk>

> From: phillip.lord@newcastle.ac.uk (Phillip Lord)
> Cc: <help-gnu-emacs@gnu.org>
> Date: Tue, 10 Mar 2015 12:37:15 +0000
> 
> >> which is an awful lot of functions to be called on every keypress. I
> >> realise that I may have gone a bit overboard here, especially as five of
> >> those functions are mine!
> >
> > The question is: what do those hook do, on average?  If they are very
> > lightweight (profile them to see if they are), then this isn't your
> > villain.
> >
> > Also, try removing most of the hooks when you see sluggish operation,
> > and see if that brings any significant speedup; if not, these aren't
> > what you are looking for.
> 
> Saw Stefan's post and think these are a red-herring also.

So if turning on GC messages doesn't give any hints, I'd suggest to
wait until you see a sluggish cursor movement, then start a CPU
profiler, perform several such cursor movements, produce the report,
and post that here.



  reply	other threads:[~2015-03-10 19:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 11:48 Emacs Slowdown Phillip Lord
2015-03-09 16:16 ` Eli Zaretskii
2015-03-09 21:50   ` Stefan Monnier
2015-03-10 12:37   ` Phillip Lord
2015-03-10 19:00     ` Eli Zaretskii [this message]
2015-03-09 21:59 ` Stefan Monnier
2015-03-10 12:39   ` Phillip Lord
2015-03-10 13:22     ` Stefan Monnier
2015-03-12 11:36 ` Phillip Lord
2015-03-16 11:41   ` Phillip Lord
2015-03-16 12:36     ` Stefan Monnier
2015-03-16 16:51       ` Phillip Lord
2015-03-18 12:23         ` Phillip Lord
2015-03-18 12:44           ` Stefan Monnier
2015-03-18 14:13             ` Phillip Lord
2015-03-18 14:53               ` Stefan Monnier
2015-03-18 16:34                 ` Phillip Lord
2015-03-18 16:32             ` Eli Zaretskii
2015-03-18 17:04               ` Phillip Lord

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=8361a865k5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).