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: Mon, 12 Mar 2018 13:09:13 -0400 [thread overview]
Message-ID: <CAM-tV--qVahaOrjwusu8GBYW7VU=h_Psb6WSUBjh3Vm3hwNOnQ@mail.gmail.com> (raw)
In-Reply-To: <CACspjXcYJGDR0sro1FRsVATOvD1eqe7isg5vMD4FzNz4Fa5LvA@mail.gmail.com>
On Mon, Mar 12, 2018 at 12:08 PM, Shuguang Sun <shuguang@gmail.com> wrote:
> FYI. If put (package-initialize) before custom-set-variables,
>>>> before custom-set-variables : 3.637 sec <<<
> Loading image-file...done
> Loading time...done
> Loading completion...done
> Loading elec-pair...done
> Loading icomplete...done
> Loading ido...done
> Loading avoid...done
> Loading savehist...done
> Loading paren...done
>>>> custom-set-variables time: 10.080 sec <<<
>
> Don't know whether autoloads being triggered. It is hard to test one by one.
Try
...
(require 'trace)
(trace-function 'do-after-load-evaluation)
(custom-set-variables ...)
(untrace-function 'do-after-load-evaluation)
and see if there is a difference in the *trace-output* buffer when you
call package-initialize first.
Maybe also do (mapc #'require '(image-file time completion elec-pair
ido avoid savehist paren)) to get the known loads (which I see listed
in your output above) out of the way.
next prev parent reply other threads:[~2018-03-12 17:09 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 [this message]
2018-03-13 10:34 ` Shuguang Sun
2018-03-14 1:38 ` Noam Postavsky
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
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='CAM-tV--qVahaOrjwusu8GBYW7VU=h_Psb6WSUBjh3Vm3hwNOnQ@mail.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 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).