unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrey Orst <andreyorst@gmail.com>
Cc: 46350@debbugs.gnu.org
Subject: bug#46350: 28.0.50; touchpad-scrolling-eats-lots-of-cpu-samples
Date: Sun, 07 Feb 2021 19:49:37 +0200	[thread overview]
Message-ID: <83h7mnn4y6.fsf@gnu.org> (raw)
In-Reply-To: <CAAKhXoaQz3bpE7MZ8oXe-0rGVcRCVh=w52zjNnanh4UwzU_+qQ@mail.gmail.com> (message from Andrey Orst on Sun, 7 Feb 2021 20:23:09 +0300)

> From: Andrey Orst <andreyorst@gmail.com>
> Date: Sun, 7 Feb 2021 20:23:09 +0300
> Cc: 46350@debbugs.gnu.org
> 
> > Add a call to 'message' to mwheel-scroll, and have it show a counter
> > that counts up?
> 
> I've did as you've suggested. When scrolling buffer of 1405 lines from
> bottom to the top (while emacs is unresponsive) mwheel-scroll function
> seems to be called about ~1351 times. Single fast flick over touchpad
> produces ~40 calls to mwheel-scroll.

1350 calls during what time, approximately? less than a second?

I don't think Emacs can scroll so fast, one line at a time.  Note that
when you scroll with the scroll-bar, Emacs doesn't call
scroll-up/down, it just goes to a suitably calculated buffer position.
Which is why scroll-bar scrolling is much faster.  But I don't see how
we can do something similar with the mouse-wheel, since it doesn't
allow to calculate the buffer position to go to; Emacs needs to do
that calculation itself, and that what makes the scrolling so much
slower.

> > What is the size of the buffer that it scrolls almost instantly to
> > BOB?  How many lines?
> 
> 1405 lines. I'm testing this on bundled lisp-mode.el

Which explains why it scrolls in one go: 1405 ≅ 1350.

So, once we've established that the touchpad injects 1-line scroll
requests at such a high rate, what else needs to be investigated here?





  reply	other threads:[~2021-02-07 17:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-06 17:33 bug#46350: 28.0.50; touchpad-scrolling-eats-lots-of-cpu-samples Andrey Orst
2021-02-06 17:59 ` Eli Zaretskii
2021-02-06 18:34   ` Andrey Orst
2021-02-06 18:55     ` Andrey Orst
2021-02-06 19:05       ` Eli Zaretskii
2021-02-06 19:02     ` Eli Zaretskii
2021-02-06 19:47       ` Andrey Orst
2021-02-06 20:03         ` Eli Zaretskii
2021-02-07 17:23           ` Andrey Orst
2021-02-07 17:49             ` Eli Zaretskii [this message]
2021-02-07 18:33               ` Andrey Orst
2021-02-07 18:44                 ` Eli Zaretskii
2021-02-07 18:52                   ` Andrey Orst
2021-02-07 19:05                     ` Eli Zaretskii
2021-02-07 19:37                       ` Lars Ingebrigtsen
2021-02-07 19:47                         ` Eli Zaretskii
2021-02-07 20:54                           ` Lars Ingebrigtsen
2021-02-07 22:16                     ` Alan Third
2021-02-07 22:22                       ` Andrey Orst
2021-02-07 22:24                         ` Alan Third
2021-02-07 22:30                           ` Andrey Orst
2021-02-08 10:12                             ` Andrey Orst
2021-02-08 14:35                               ` Andrey Orst
2021-02-08 15:28                                 ` Eli Zaretskii
2021-02-08 15:31                                   ` Andrey Orst
2021-02-08 15:19                               ` Eli Zaretskii

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=83h7mnn4y6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=46350@debbugs.gnu.org \
    --cc=andreyorst@gmail.com \
    /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).