From: Alex Bennee <kernel-hacker@bennee.com>
To: "A.Politz" <politza@googlemail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Tracking down why emacsclient -c is so slow
Date: Sat, 22 Aug 2009 12:27:46 +0100 [thread overview]
Message-ID: <b2cdc9f30908220427s68133ff8jd0eba18d3566c3ed@mail.gmail.com> (raw)
In-Reply-To: <1b4247eb-cf93-41ad-b118-5e6c0270edd5@s13g2000yql.googlegroups.com>
2009/8/22 A.Politz <politza@googlemail.com>:
> On Aug 22, 10:10 am, Alex Bennee <kernel-hac...@bennee.com> wrote:
<snip>
>
>>after-make-frame-functions at Fri Aug 21 19:18:21 2009
>>server-visit-hook at Fri Aug 21 19:18:25 2009
>>(No files need saving)
>
> This together seem to imply, that the time is spent in one of the
> after-make-frame-functions.
>
> Have you done this with 'emacs -Q --daemon' ?
>
Yes, it does seem to be something introduced by my .emacs frame
modification functions. Adding some additional instrumentation made it
go away although I have no idea why [1].
> elp-instrument-list won't allow to profile all functions,
> but you can do it anyway. Expect your emacs to be broken
> afterwards.
>
> (progn
> (require 'elp)
> (elp-instrument-list
> (mapcar #'intern
> (all-completions "" obarray
> #'(lambda (sym)
> (and (elp-profilable-p sym)
> (not (eq sym '+))))))))
Hmm, my version of elp doesn't have the elp-profilable-p
[1] http://www.bennee.com/~alex/news.php?wl_mode=more&wl_eid=1292
--
Alex, homepage: http://www.bennee.com/~alex/
http://www.half-llama.co.uk
prev parent reply other threads:[~2009-08-22 11:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 18:25 Tracking down why emacsclient -c is so slow Alex Bennee
2009-08-21 18:54 ` Peter Dyballa
2009-08-22 8:10 ` Alex Bennee
2009-08-22 10:35 ` Peter Dyballa
2009-08-22 11:33 ` Alex Bennee
2009-08-22 11:58 ` Peter Dyballa
2009-08-22 12:47 ` Alex Bennee
2009-08-22 14:03 ` Alex Bennee
2009-08-22 14:26 ` Alex Bennee
[not found] ` <mailman.5119.1250928641.2239.help-gnu-emacs@gnu.org>
2009-08-22 9:53 ` A.Politz
2009-08-22 11:27 ` Alex Bennee [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b2cdc9f30908220427s68133ff8jd0eba18d3566c3ed@mail.gmail.com \
--to=kernel-hacker@bennee.com \
--cc=help-gnu-emacs@gnu.org \
--cc=politza@googlemail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.