From: Eval Exec <execvy@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: How to let `profiler-report` show more info for `redisplay_internal`?
Date: Mon, 2 Sep 2024 20:25:28 +0800 [thread overview]
Message-ID: <CAKfPJDrxSB8t4Wmo-MNgV1Dx8AKCPO9WVXMSWLWGNJhJquNRfw@mail.gmail.com> (raw)
In-Reply-To: <86seui8e8p.fsf@gnu.org>
Thank you!
On Mon, Sep 2, 2024 at 7:52 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Date: Mon, 2 Sep 2024 11:02:50 +0800
> > From: Eval EXEC <execvy@gmail.com>
> >
> > 103 94% - redisplay_internal (C function)
> > 3 2% - eval
> > 2 1% - minions--prominent-modes
> > 2 1% - cl-remove-if-not
> > 2 1% - cl-remove
> > 1 0% cl-ldiff
> > 1 0% - mode--line-format-right-align
> > 1 0% - eval
> > 1 0% - minions--prominent-modes
> > 1 0% - cl-remove-if-not
> > 1 0% cl-remove
> > 6 5% - timer-event-handler
> > 6 5% - apply
> > 6 5% - #<native-comp-function
> > F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_23>
> > 6 5% jit-lock-context-fontify
> > 0 0% ...
> > ```
> >
> >
> > I noticed that `redisplay_internal` is consuming 94% of the CPU, but the
> > sum of the child items below `redisplay_internal` is less than 2%. Where
> > is the remaining 92% going? I'd like to see a more detailed CPU profile
> > for `redisplay_internal`.
> >
> > Is it possible to get a detailed CPU profile for `redisplay_internal`?
>
> No, you cannot, because redisplay_internal is written in C, and
> profiler.el can only analyze profiles of Lisp code.
>
> You need to use a tool like perf for profiling C code.
>
> Sorry.
prev parent reply other threads:[~2024-09-02 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 3:02 How to let `profiler-report` show more info for `redisplay_internal`? Eval EXEC
2024-09-02 11:51 ` Eli Zaretskii
2024-09-02 11:52 ` Eli Zaretskii
2024-09-02 12:25 ` Eval Exec [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKfPJDrxSB8t4Wmo-MNgV1Dx8AKCPO9WVXMSWLWGNJhJquNRfw@mail.gmail.com \
--to=execvy@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.