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 20:44:57 +0200 [thread overview]
Message-ID: <83czxbn2dy.fsf@gnu.org> (raw)
In-Reply-To: <CAAKhXoYcXnhs0EwTVA8BCyC6aFmb9nOW-qD3JQnzaSxXCUs=YA@mail.gmail.com> (message from Andrey Orst on Sun, 7 Feb 2021 21:33:25 +0300)
> From: Andrey Orst <andreyorst@gmail.com>
> Date: Sun, 7 Feb 2021 21:33:25 +0300
> Cc: 46350@debbugs.gnu.org
>
> On Sun, Feb 7, 2021 at 8:49 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > 1350 calls during what time, approximately? less than a second?
>
> If you've watched the video I've linked
I cannot watch that video, sorry. But I don't think it matters, see
below.
> you can get a sense of what
> time it takes -- about 15 seconds. Or more if I continue swyping
> rapidly, since Emacs just sits at the bottom eating all input until I
> stop.
I didn't ask how much time it takes Emacs to process the inputs. I
asked how much time did it take you to generate them by moving your
finger on the touchpad. I very much doubt the answer to that is 15
sec.
> Touchpad generates about 20-30 inputs per swipe, so I think ~90 inputs
> is maximum human can produce in 1 second
~100 1-line scrolls per second is also a lot, for what Emacs must do
to scroll.
> Can Emacs poll mouse events less frequently?
Emacs doesn't poll the mouse. The mouse events are received from the
X event queue, together with all the other events: keyboard input,
expose events, etc. We read the events from X and then process them
one by one.
> > 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?
>
> There I was talking about progressive speed turned on, as it builds up
> almost instantly with my touchpad producing 30 inputs per swipe.
Sorry, I don't understand: what builds up?
next prev parent reply other threads:[~2021-02-07 18:44 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
2021-02-07 18:33 ` Andrey Orst
2021-02-07 18:44 ` Eli Zaretskii [this message]
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=83czxbn2dy.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).