emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to let `profiler-report` show more info for `redisplay_internal`


From: Eval Exec
Subject: Re: How to let `profiler-report` show more info for `redisplay_internal`?
Date: Mon, 2 Sep 2024 20:25:28 +0800

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.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]