From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: dim1212k@gmail.com, emacs-devel@gnu.org
Subject: Re: Garbage collector: is 800kb a good default?
Date: Thu, 09 Apr 2020 22:08:25 +0300 [thread overview]
Message-ID: <834ktso4t2.fsf@gnu.org> (raw)
In-Reply-To: <jwv5ze84ifk.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 09 Apr 2020 14:42:56 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: dim1212k@gmail.com, emacs-devel@gnu.org
> Date: Thu, 09 Apr 2020 14:42:56 -0400
>
> > Let's not forget that running GC while Emacs is idle will make Emacs
> > less responsive if the user starts typing while GC is in progress,
>
> The argument for GC-when-idle goes that if this happens it's not really
> worse than what we have now, because if the GC hadn't started "before
> the user starts typing", it would have run as part of the command
> launched by the user, so from the user's point of view there's no
> noticeable difference.
The difference is that when an idle timer runs a long uninterruptible
calculation, the user thinks Emacs is idle, so having a character
appear, or Emacs respond to a command with a prompt, after a
significant delay makes a very bad UX. By contrast, when a command is
running, the user will normally know that Emacs isn't idle, so a
delayed response will be less of a surprise.
> > Also, we already try running GC each time Emacs becomes idle.
>
> Do we? I thought so as well, but I couldn't see any evidence of it in
> the code.
It's in keyboard.c, right after we auto-save when enough idle time has
passed:
/* If there is still no input available, ask for GC. */
if (!detect_input_pending_run_timers (0))
maybe_gc ();
next prev parent reply other threads:[~2020-04-09 19:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 11:59 Garbage collector: is 800kb a good default? Dmitrii Korobeinikov
2020-04-09 12:33 ` Eli Zaretskii
2020-04-09 13:44 ` Dmitrii Korobeinikov
2020-04-09 14:02 ` Eli Zaretskii
2020-04-09 14:46 ` Dmitrii Korobeinikov
2020-04-09 16:42 ` Eli Zaretskii
2020-04-10 16:40 ` Dmitrii Korobeinikov
2020-04-09 19:05 ` Stefan Monnier
2020-04-10 16:26 ` Dmitrii Korobeinikov
2020-04-09 18:48 ` Stefan Monnier
2020-04-10 14:26 ` Bruno Félix Rezende Ribeiro
2020-04-10 16:49 ` Eli Zaretskii
2020-04-10 18:26 ` Bruno Félix Rezende Ribeiro
2020-04-10 18:53 ` Paul Eggert
2020-04-09 13:47 ` Stefan Monnier
2020-04-09 14:20 ` Dmitrii Korobeinikov
2020-04-09 14:23 ` Eli Zaretskii
2020-04-09 18:42 ` Stefan Monnier
2020-04-09 19:08 ` Eli Zaretskii [this message]
2020-04-09 19:31 ` Stefan Monnier
2020-04-10 6:19 ` Eli Zaretskii
2020-04-10 13:03 ` Stefan Monnier
2020-04-10 13:42 ` Eli Zaretskii
2020-04-10 14:34 ` Stefan Monnier
2020-04-10 14:38 ` Stefan Monnier
2020-04-10 15:37 ` Eli Zaretskii
2020-04-10 15:52 ` Andrea Corallo
2020-04-10 16:45 ` Stefan Monnier
2020-04-10 17:18 ` Andrea Corallo
2020-04-09 14:48 ` Andrea Corallo
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834ktso4t2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dim1212k@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.