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: Sat, 06 Feb 2021 21:02:04 +0200 [thread overview]
Message-ID: <838s81nhoz.fsf@gnu.org> (raw)
In-Reply-To: <CAAKhXoa80U+R3nDcvBzJxyy_CLRyczMWKUYCTVWxF-skg+om4Q@mail.gmail.com> (message from Andrey Orst on Sat, 6 Feb 2021 21:34:29 +0300)
> From: Andrey Orst <andreyorst@gmail.com>
> Date: Sat, 6 Feb 2021 21:34:29 +0300
> Cc: 46350@debbugs.gnu.org
>
> > Please load mwheel.el (NOT the .elc file!), and then profile the slow
> > scrolling again and show a fully-expanded profile. That might help us
> > understand what part of mwheel-scroll takes the lion's share of CPU
> > cycles.
>
> Here's whole report expanded (btw can't find if there's expand-all feature?):
Yes, "C-u RET".
> 11593 91% - command-execute
> 11549 91% - funcall-interactively
> 11542 91% - mwheel-scroll
> 11536 91% - let*
> 11420 90% - condition-case
> 11381 90% - unwind-protect
> 11377 90% - let
> 11373 90% - cond
> 11372 90% - condition-case
> 10868 86% - funcall
> 324 2% - scroll-down
> 263 2% - jit-lock-function
> 255 2% - jit-lock-fontify-now
> 235 1% - jit-lock--run-functions
I cannot make sense out of this: this profile says that funcall takes
most of the time, and the function it calls, scroll-down, takes almost
no time? Does anyone have any idea what could be going on here?
If this is just some artifact of "M-x profile", and most of the time
is spent in scroll-down, then I'm not sure what can be done, nor why
you see something I don't. Do you use a large frame and/or a small
font? And how many mouse-wheel events Emacs receives in your
scenario, anyway?
Oh, and what happens if you raise gc-cons-threshold to a large value?
next prev parent reply other threads:[~2021-02-06 19:02 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 [this message]
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
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=838s81nhoz.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).