From: execvy@gmail.com
To: Eli Zaretskii <eliz@gnu.org>, 74813@debbugs.gnu.org
Subject: bug#74813: 31.0.50; scroll-down is 10x slower and laggy than scroll-up
Date: Fri, 10 Jan 2025 16:04:47 +0800 [thread overview]
Message-ID: <7795e06c-df0a-4cf3-ab04-7a20a4ddd2c4@gmail.com> (raw)
In-Reply-To: <86h66714ih.fsf@gnu.org>
My auto-repeat rate is 100 times/second
It's hard to notice performance difference by eyes and hands.
You can do profiler-start (cpu) and profiler-report, then you will notice
the profiler result is totally different.
On 1/10/25 4:01 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Fri, 10 Jan 2025 15:30:34 +0800
> > From: execvy@gmail.com
> >
> > I try to reproduce on `emacs -Q` for this file: https://raw.githubusercontent.com/bitcoin/bitcoin/refs/heads/master/src/secp256k1/src/precomputed_ecmult.c
> >
> > It's fundamental-mode, then I notice `C-v` and `M-v` 's scroll-up and scroll-down have performance difference: C-v is more smoother than scroll-up.
>
> I've now tried that file in fundamental-mode, and I don't see any
> perceptible differences between C-v and M-v. For example, scrolling
> from top to bottom by leaning on C-v takes 35 sec, and scrolling
> bottom to top with M-v takes the same 35 sec.
>
> What is your auto-repeat rate for the keyboard? That is, if you press
> and hold C-v, how many key presses per second does your system
> produce?
>
next prev parent reply other threads:[~2025-01-10 8:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 7:59 bug#74813: 31.0.50; scroll-down is 10x slower and laggy than scroll-up Eval Exec
2024-12-12 9:11 ` Eli Zaretskii
2024-12-28 10:59 ` Eli Zaretskii
2024-12-28 13:31 ` Eval Exec
2025-01-04 12:05 ` Eli Zaretskii
2025-01-05 3:05 ` Eval Exec
2025-01-10 7:30 ` execvy
2025-01-10 8:01 ` Eli Zaretskii
2025-01-10 8:04 ` execvy [this message]
2025-01-10 8:20 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7795e06c-df0a-4cf3-ab04-7a20a4ddd2c4@gmail.com \
--to=execvy@gmail.com \
--cc=74813@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.