From: Eli Zaretskii <eliz@gnu.org>
To: execvy@gmail.com
Cc: 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 10:20:55 +0200 [thread overview]
Message-ID: <86frlr13mg.fsf@gnu.org> (raw)
In-Reply-To: <7795e06c-df0a-4cf3-ab04-7a20a4ddd2c4@gmail.com> (execvy@gmail.com)
> Date: Fri, 10 Jan 2025 16:04:47 +0800
> From: execvy@gmail.com
>
> My auto-repeat rate is 100 times/second
Mine is 30/sec. Maybe this is the reason for what you see.
Programmatically, M-v needs to do more than C-v does, so if your CPU
is not powerful enough, maybe Emacs cannot keep up with 100 keys per
second moving back.
If this is the reason, then it's expected.
> 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.
The profiler result is expected to be different, because M-v invokes
different functions than C-v does.
What I measured is the total time of scrolling through the entire
file, and I didn't see any difference, as reported: 35 sec both down
and up. I measured the time with a stopper, not by eyes.
prev parent reply other threads:[~2025-01-10 8:20 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
2025-01-10 8:20 ` 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=86frlr13mg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74813@debbugs.gnu.org \
--cc=execvy@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).