unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Is Emacs buffer scroll/redisplay slow?
Date: Sun, 19 Jan 2020 18:15:54 +0100	[thread overview]
Message-ID: <CAFgFV9Pcq7nsSFK1b5w-mbiEw_kt1v+867r+w0sy2+ZK_iej8A@mail.gmail.com> (raw)
In-Reply-To: <83y2u3xwm4.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]

Le dim. 19 janv. 2020 à 17:02, Eli Zaretskii <eliz@gnu.org> a écrit :

>
> > We could expect emacs to be a little bit more reactive here.
>
> Please repeat the experiment in a fresh "emacs -Q" right after
> starting it, then, after you finish scrolling, see what is the amount
> of CPU time reported by utilities such as PsList.  Alternatively, look
> at the load average value displayed by another Emacs session.
>
> In my testing, when I lean on the DOWN arrow, the system load never
> raises above 0.25, which means 3/4th of the time Emacs is idle.  My
> keyboard's auto-repeat rate is 30 characters per second, which means
> Emacs uses up about 7 msec (1000 / 30 / 4) to process every DOWN-arrow
> keypress, and that includes all the redisplay code, JIT font-lock
> etc.  I'm not sure I agree to call this "slow".
>

Ok, thanks for the explanation which makes sense. I was afraid that elisp
be a drag here,
but it does not seem to account for too much. And it is on par with other
code editors (I tried
PyCharm to compare)

(BTW, my keyboard is also on the fastest auto-repeat setting ... but there
are ways to speed it
 over the limit imposed by the control panel of windows)

Fabrice

[-- Attachment #2: Type: text/html, Size: 1688 bytes --]

  reply	other threads:[~2020-01-19 17:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-19  9:34 Is Emacs buffer scroll/redisplay slow? Fabrice Popineau
2020-01-19 11:51 ` Alan Mackenzie
2020-01-19 14:24   ` Fabrice Popineau
2020-01-19 15:28     ` Eli Zaretskii
2020-01-19 15:34       ` Fabrice Popineau
2020-01-19 16:02         ` Eli Zaretskii
2020-01-19 17:15           ` Fabrice Popineau [this message]
2020-01-19 22:20     ` Stefan Monnier
2020-01-20  0:23       ` Fabrice Popineau
2020-01-20 13:20         ` Stefan Monnier

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=CAFgFV9Pcq7nsSFK1b5w-mbiEw_kt1v+867r+w0sy2+ZK_iej8A@mail.gmail.com \
    --to=fabrice.popineau@gmail.com \
    --cc=acm@muc.de \
    --cc=eliz@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).