From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Is it possible to profile elisp?
Date: Sun, 20 Nov 2022 22:20:55 +0200 [thread overview]
Message-ID: <83fsed4btk.fsf@gnu.org> (raw)
In-Reply-To: <2BB789D5-7DC8-4A5E-983E-A8595895A464@easesoftware.com> (message from Perry Smith on Sun, 20 Nov 2022 08:17:04 -0600)
> From: Perry Smith <pedz@easesoftware.com>
> Date: Sun, 20 Nov 2022 08:17:04 -0600
>
> I do a grep and get some results into the *grep* buffer. The hits happen to be in Org mode files if that matters.
>
> I do C-X ` and it takes 5 seconds to bring up the buffer. A next C-X ` are in the same file and are instant. But the one that has to open a different file again takes 4 to 5 seconds.
>
> This by itself doesn’t bother me that much. But I’m actually chasing weird problems and I’m wondering if this is connected to it or not.
>
> The weird problems are with lsp-mode using a package called lsp-tailwindcss. It is suppose to pop up completion suggestions. Every once in a VERY great while, it does. But usually it does not. I can pause and not enter any keys for a minute and no suggestions pop up. I have
>
> company-minimum-prefix-length set to 1 and company-idle-delay set to 0.0. If I set the idle time to 0.5 and prefix length to 2, the completions pop up but I have to sit for about 2 seconds before anything pops up.
>
> So… I’m theorizing that I’ve got something wasting time or is horribly inefficient but I have no idea how to track it down.
>
> I’m on one of Apple’s best / latest laptops so I believe I have plenty of horsepower and the CPU stats are close to 0.
I'm not sure I understand what you are after, but Emacs has a built-in
profiler, see profiler-start.
next prev parent reply other threads:[~2022-11-20 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 14:17 Is it possible to profile elisp? Perry Smith
2022-11-20 20:20 ` Eli Zaretskii [this message]
2022-11-21 11:42 ` Alessandro Bertulli
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=83fsed4btk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).