[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Elisp native profiler
From: |
Stefan Monnier |
Subject: |
Re: Elisp native profiler |
Date: |
Sat, 29 Sep 2012 12:06:21 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux) |
> Is the cpu profile below (obtained with the above recipe) reasonable?
Yes.
> Why do functions like scroll-up-command and jit-lock-function appear
> twice or three times, once under call-interactively, the other time by
> themselves or under scroll-up?
I'd guess it's because of the FIXME in profiler-call-tree-build-1.
I.e. you should be able to work around this limitation by increasing
profiler-max-stack-depth.
Stefan
> (Should we rename "Automatic GC" like we did with redisplay?)
As you may see, it's handled very specially, and is presented always at
top-level. I basically treat it as a separate (cooperative) thread.
So "Automatic GC" is meant as the name of the "thread" more than the
name of the function.
Stefan
- Re: Elisp native profiler, (continued)
- Re: Elisp native profiler, Stefan Monnier, 2012/09/26
- Re: Elisp native profiler, Eli Zaretskii, 2012/09/26
- Re: Elisp native profiler, Eli Zaretskii, 2012/09/26
- Re: Elisp native profiler, Stefan Monnier, 2012/09/26
- Re: Elisp native profiler, Eli Zaretskii, 2012/09/26
- Re: Elisp native profiler, Stefan Monnier, 2012/09/26
- Re: Elisp native profiler, Tomohiro Matsuyama, 2012/09/26
- Re: Elisp native profiler, Stefan Monnier, 2012/09/27
- Re: Elisp native profiler, Paul Eggert, 2012/09/30
- Re: Elisp native profiler, Eli Zaretskii, 2012/09/29
- Re: Elisp native profiler,
Stefan Monnier <=
- Re: Elisp native profiler, Eli Zaretskii, 2012/09/29
- Re: Elisp native profiler, Stefan Monnier, 2012/09/29
- Re: Elisp native profiler, Eli Zaretskii, 2012/09/30
Re: Elisp native profiler, Juanma Barranquero, 2012/09/25