From: Ergus <spacibba@aol.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Some performance questions.
Date: Wed, 08 Feb 2023 21:56:31 +0100 [thread overview]
Message-ID: <B22F8C97-898E-4AC8-A943-B3BA9C5452CB@aol.com> (raw)
In-Reply-To: <838rh7oqwg.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
Hi Eli:
Thanks for replying. Is the GC also improved by tree-sitter? Because it is taking a significant part of the time, as you can see in my first mail.
Thanks,
Ergus
On February 8, 2023 9:15:11 PM GMT+01:00, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Wed, 08 Feb 2023 22:09:36 +0200
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: emacs-devel@gnu.org
>>
>> > 71 45% Automatic GC
>> > 68 43% redisplay_internal
>> > jit-lock-function
>> > ...
>> > font-lock-fontify-keywords-region
>> >
>> > 37 23% c-font-lock-declarations
>> > 20 12% c-font-lock-cut-off-declarators
>> >
>> > I have not observed such lags before on GNU/Linux, so some idea what I
>> > may be doing wrong?
>> >
>> > I know Eli uses MS-Windows frequently, so, any hint?
>>
>> Try using c-ts-mode instead (assuming this is Emacs 29 and it was
>> built with tree-sitter).
>
>And if you cannot use tree-sitter, then try this:
>
> (setq jit-lock-stealth-time 16)
> (setq jit-lock-defer-contextually t)
> (setq jit-lock-stealth-load 20)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
[-- Attachment #2: Type: text/html, Size: 1864 bytes --]
next prev parent reply other threads:[~2023-02-08 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230208190819.z7xwgxm5gpbzmjrz.ref@Ergus>
2023-02-08 19:08 ` Some performance questions Ergus
2023-02-08 20:09 ` Eli Zaretskii
2023-02-08 20:15 ` Eli Zaretskii
2023-02-08 20:56 ` Ergus [this message]
2023-02-09 6:17 ` Eli Zaretskii
2023-02-09 13:14 ` Ergus
[not found] ` <20230209114928.eqpojruluur42hur@Ergus>
2023-02-09 13:46 ` Eli Zaretskii
2023-02-09 15:45 ` Ergus
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=B22F8C97-898E-4AC8-A943-B3BA9C5452CB@aol.com \
--to=spacibba@aol.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.
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).