From: Eli Zaretskii <eliz@gnu.org>
To: Andrey Orst <andreyorst@gmail.com>
Cc: andreyorst@gmail.com, 46350@debbugs.gnu.org, alan@idiocy.org
Subject: bug#46350: 28.0.50; touchpad-scrolling-eats-lots-of-cpu-samples
Date: Mon, 08 Feb 2021 17:19:41 +0200 [thread overview]
Message-ID: <83ft26lh82.fsf@gnu.org> (raw)
In-Reply-To: <CAAKhXoa_S0e8mieKfi8KZp_OuLAnW2w7M1xeSK=7C_6heTJ3qw@mail.gmail.com> (message from Andrey Orst on Mon, 8 Feb 2021 13:12:09 +0300)
> From: Andrey Orst <andreyorst@gmail.com>
> Date: Mon, 8 Feb 2021 13:12:09 +0300
>
> Also, for some reason scrolling to the buffer's end has much less lag compared to scrolling to the beginning
> of the buffer. It's still laggy, but more manageable
Scrolling back to the beginning of buffer is more CPU-intensive,
because the functions used for scrolling can only move forward in the
buffer. So what you see is quite expected.
prev parent reply other threads:[~2021-02-08 15:19 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
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 [this message]
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=83ft26lh82.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46350@debbugs.gnu.org \
--cc=alan@idiocy.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).