* Strange profiling report
@ 2016-10-14 11:11 Fabrice Popineau
2016-10-14 13:06 ` Stefan Monnier
0 siblings, 1 reply; 2+ messages in thread
From: Fabrice Popineau @ 2016-10-14 11:11 UTC (permalink / raw)
To: Emacs developers
[-- Attachment #1: Type: text/plain, Size: 2915 bytes --]
Hi,
I'm using Emacs 25.1 compiled with MinGW64 and I got this profiling report:
- timer-event-handler 9168 52%
- apply 9096 51%
- auto-revert-buffers 7391 41%
- auto-revert-handler 7198 40%
buffer-stale--default-function 7083 40%
file-remote-p 78 0%
+ savehist-autosave 321 1%
+ company-idle-begin 111 0%
+ flycheck-handle-idle-change 16 0%
+ desktop-auto-save 13 0%
+ sp-show--pair-function 12 0%
+ org-element--cache-sync 9 0%
beacon--dec 8 0%
+ which-func-update 1 0%
+ timer-inc-time 28 0%
+ timer-activate 14 0%
timer-until 8 0%
cancel-timer-internal 3 0%
timerp 1 0%
+ command-execute 4508 25%
+ flyspell-post-command-hook 2798 15%
+ ... 929 5%
+ redisplay_internal (C function) 125 0%
+ beacon--post-command 20 0%
+ global-hl-line-highlight 17 0%
+ sp--save-pre-command-state 16 0%
+ delete-selection-pre-hook 12 0%
global-hl-line-unhighlight 9 0%
+ company-post-command 4 0%
+ projectile-global-mode-check-buffers 2 0%
+ prelude-global-mode-check-buffers 1 0%
+ which-key--hide-popup 1 0%
+ flycheck-perform-deferred-syntax-check 1 0%
sml/generate-position-help 1 0%
+ winner-save-old-configurations 1 0%
The buffer-stale--default-function worries me: how could it use so much
time ?
Moreover, it is an elisp function, so why the profiler doesn't report about
the
inner functions?
Thanks for any clue,
Fabrice
[-- Attachment #2: Type: text/html, Size: 6148 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Strange profiling report
2016-10-14 11:11 Strange profiling report Fabrice Popineau
@ 2016-10-14 13:06 ` Stefan Monnier
0 siblings, 0 replies; 2+ messages in thread
From: Stefan Monnier @ 2016-10-14 13:06 UTC (permalink / raw)
To: emacs-devel
> The buffer-stale--default-function worries me: how could it use so
> much time ? Moreover, it is an elisp function, so why the profiler
> doesn't report about the inner functions?
Good questions. I think you'd need to instrument the code to try and
get more detailed info in order to figure that out.
Seeing how many times it's called might give a bit more of a clue?
Stefan
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-10-14 13:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-10-14 11:11 Strange profiling report Fabrice Popineau
2016-10-14 13:06 ` Stefan Monnier
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).