From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Strange profiling report
Date: Fri, 14 Oct 2016 13:11:28 +0200 [thread overview]
Message-ID: <CAFgFV9NXZWspH4j0n_0M7AFdJ07XcR31T5N_f7nmzk4-Y6bg7w@mail.gmail.com> (raw)
[-- 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 --]
next reply other threads:[~2016-10-14 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 11:11 Fabrice Popineau [this message]
2016-10-14 13:06 ` Strange profiling report Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFgFV9NXZWspH4j0n_0M7AFdJ07XcR31T5N_f7nmzk4-Y6bg7w@mail.gmail.com \
--to=fabrice.popineau@gmail.com \
--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 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).