[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Elisp native profiler
From: |
Eli Zaretskii |
Subject: |
Re: Elisp native profiler |
Date: |
Sat, 29 Sep 2012 18:18:42 +0200 |
> From: Stefan Monnier <address@hidden>
> Cc: address@hidden
> Date: Sat, 29 Sep 2012 12:06:21 -0400
>
> > 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.
Yes, looks more reasonable with 64 (vs default 16), see below. Should
the default be increased?
- call-interactively 160 87%
- scroll-up-command 112 61%
- scroll-up 112 61%
- jit-lock-function 106 58%
- jit-lock-fontify-now 106 58%
- byte-code 106 58%
- run-hook-with-args 106 58%
- font-lock-fontify-region 106 58%
- c-font-lock-fontify-region 106 58%
- font-lock-default-fontify-region 94 51%
- font-lock-fontify-keywords-region 94 51%
- c-font-lock-declarations 63 34%
- c-find-decl-spots 63 34%
- #<compiled 0xd4164d> 62 34%
+ c-parse-state 12 6%
+ c-determine-limit 12 6%
+ c-beginning-of-decl-1 11 6%
+ c-forward-decl-or-cast-1 7 3%
+ c-cheap-inside-bracelist-p 7 3%
+ c-backward-sws 5 2%
+ c-forward-label 3 1%
+ c-backward-token-2 3 1%
looking-at 1 0%
looking-at 1 0%
- c-font-lock-enclosing-decls 22 12%
- c-beginning-of-decl-1 19 10%
- byte-code 19 10%
- c-beginning-of-statement-1 12 6%
+ byte-code 9 4%
+ c-backward-sws 3 1%
+ c-in-knr-argdecl 7 3%
+ c-parse-state 3 1%
+ c-font-lock-complex-decl-prepare 3 1%
+ #<compiled 0xd50bf9> 2 1%
re-search-forward 2 1%
+ #<compiled 0xd50bdb> 1 0%
+ #<compiled 0xd53453> 1 0%
- mapc 12 6%
- #<compiled 0x4015749> 12 6%
- c-context-set-fl-decl-start 12 6%
- c-set-fl-decl-start 12 6%
+ c-beginning-of-decl-1 8 4%
+ c-determine-limit 3 1%
+ c-literal-limits 1 0%
- list 48 26%
- read-extended-command 48 26%
- completing-read 48 26%
- completing-read-default 48 26%
- read-from-minibuffer 48 26%
redisplay_internal (C function) 1 0%
- redisplay_internal (C function) 11 6%
- jit-lock-function 8 4%
- jit-lock-fontify-now 8 4%
- byte-code 8 4%
- run-hook-with-args 8 4%
- font-lock-fontify-region 8 4%
- c-font-lock-fontify-region 8 4%
- font-lock-default-fontify-region 8 4%
- font-lock-fontify-keywords-region 8 4%
- c-font-lock-declarations 4 2%
+ c-find-decl-spots 4 2%
re-search-forward 2 1%
- c-font-lock-enclosing-decls 2 1%
+ c-parse-state 2 1%
Automatic GC 11 6%
- Re: Elisp native profiler, (continued)
- 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, 2012/09/29
- Re: Elisp native profiler,
Eli Zaretskii <=
- 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