Closed amosbird closed 6 years ago
I haven't managed to get esup working on spacemacs, which was annoying since I used up until recently. I'm unsure of the root cause. It's likely related to some of the other bugs about esup choking on .elc files.
The same happens with Doom Emacs even with all .elc files deleted:
ERROR: the child emacs had the following errors:
ERROR(profile-sexp) at /home/adam/.emacs.d/init.el:34: (wrong-type-argument stringp (concat user-emacs-directory core/core))
Results will be incomplete due to errors.
the line esup is bailing out is:
(require 'core (concat user-emacs-directory "core/core"))
Guys. you can profile Spacemacs just fine, it adds a few additional command line options:
--profile
will display profiling information on startup--timed-requires
will display the time taken by each require
commandsAlso, the unobvious thing about --timed-requires
-- it creates a buffer (*load-times*
), but it might stay in background, so you have to switch to it. Took me a while to realize.
This is probably because esup doesn't handle the case where a path is provided as the second arg for require. I just created a whole new test suite, so tackling this will be much easier.
Should be fixed. Please re-open if not.
Guys. you can profile Spacemacs just fine, it adds a few additional command line options:
Right, but if you a slow line in a file, the require just narrows it down to the file. The goal of esup is to provide sexp-level profiling info.
Hm, when I esup spacemacs (on Emacs 27) I only see traces of diff-mode.elc
and vc-get.elc
and very low startup time:
Total User Startup Time: 0.006sec Total Number of GC Pauses: 0 Total GC Time: 0.000sec
Hi, how can I use esup to profile spacemacs' start time? Currently I got