unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ergus <spacibba@aol.com>
Cc: emacs-devel@gnu.org
Subject: Re: Some performance questions.
Date: Thu, 09 Feb 2023 08:17:37 +0200	[thread overview]
Message-ID: <837cwrnz0e.fsf@gnu.org> (raw)
In-Reply-To: <B22F8C97-898E-4AC8-A943-B3BA9C5452CB@aol.com> (message from Ergus on Wed, 08 Feb 2023 21:56:31 +0100)

> Date: Wed, 08 Feb 2023 21:56:31 +0100
> From: Ergus <spacibba@aol.com>
> CC: emacs-devel@gnu.org
> 
> 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.

Tree-sitter based modes do less processing in Lisp (the buffer parsing
is doen by the tree-sitter and the grammar libraries, entirely in C
and C++), so they should in general produce less garbage and require
less GC, yes.

Turning on jit-stealth also lowers the GC pressure because it
fontifies buffers during idle time, so by the time you get to actually
editing a buffer it is already fontified, and thus all the garbage
produced by fontifications was already produced and collected; the
editing itself will produce much less garbage.

Finally, I see that in my customizations I increase gc-cons-threshold
to 1800000 (from the default of 800000), so maybe try that as well.



  reply	other threads:[~2023-02-09  6:17 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
2023-02-09  6:17         ` Eli Zaretskii [this message]
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=837cwrnz0e.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=spacibba@aol.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).