From: Noam Postavsky <npostavs@gmail.com>
To: Shuguang Sun <shuguang@gmail.com>
Cc: 30731@debbugs.gnu.org
Subject: bug#30731: Slower startup using March (27.0.50) build in windows
Date: Tue, 13 Mar 2018 21:38:41 -0400 [thread overview]
Message-ID: <87d107xwpp.fsf@gmail.com> (raw)
In-Reply-To: <CACspjXdXfB_KzHPFfxciJCVQ_ZqJLDYF-xmddm2bgD7245VUeA@mail.gmail.com> (Shuguang Sun's message of "Tue, 13 Mar 2018 18:34:16 +0800")
Shuguang Sun <shuguang@gmail.com> writes:
> The trace-log from package-earlyload has less
> do-after-load-evaluation items which are supposed to be loaded during
> the package-initialize. However, it still takes longer time for
> custom-set-variables during early package initialization.
> The two items, mail-prsvr.elc and mm-util.elc are in earlyload but
> not in lateload.
Hmm, somehow that was not so informative as I'd have hoped. Maybe
measuring each setting individually would give more info, try this:
(require 'pcase)
(defmacro split-custom-set-variables (cset-form)
(pcase cset-form
(`(custom-set-variables . ,entries)
`(progn
,@(mapcar
(pcase-lambda (`(quote (,sym . ,args)))
`(let ((t0 (current-time))
(tf nil))
(custom-set-variables (quote (,sym . ,args)))
(setq tf (current-time))
(message "setting `%s': %.3fs" ',sym
(float-time (time-subtract tf t0)))))
entries)))))
(split-custom-set-variables
(custom-set-variables
...))
next prev parent reply other threads:[~2018-03-14 1:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 16:20 bug#30731: Slower startup using March (27.0.50) build in windows Shuguang Sun
2018-03-09 1:35 ` Noam Postavsky
2018-03-11 3:25 ` Shuguang Sun
2018-03-11 17:21 ` Shuguang Sun
2018-03-11 17:39 ` Noam Postavsky
2018-03-12 1:48 ` Shuguang Sun
2018-03-12 1:52 ` Noam Postavsky
2018-03-12 16:08 ` Shuguang Sun
2018-03-12 17:09 ` Noam Postavsky
2018-03-13 10:34 ` Shuguang Sun
2018-03-14 1:38 ` Noam Postavsky [this message]
2018-03-14 5:02 ` Shuguang Sun
2018-03-19 23:41 ` Noam Postavsky
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=87d107xwpp.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=30731@debbugs.gnu.org \
--cc=shuguang@gmail.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.