From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dim1212k@gmail.com, emacs-devel@gnu.org
Subject: Re: Garbage collector: is 800kb a good default?
Date: Fri, 10 Apr 2020 10:34:02 -0400 [thread overview]
Message-ID: <jwvk12nxvjr.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83mu7jmp8l.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 Apr 2020 16:42:18 +0300")
>> > We are miscommunicating. My complaint was about the _response_ time,
>> > which is the time that passes between me pressing a key and Emacs
>> > reacting to that. In your description above it is the time between
>> > "the user hits a key" and "the command starts".
>>
>> The user can't know when Emacs reacts to the key: in both cases there's
>> no sign of life until point 4 finishes (that's assuming the command is
>> something like self-insert-command where there's no user interaction
>> *during* the command).
>
> Even for self-insert-command, I can easily know whether the command
> started or not, because I have garbage-collection-messages turned on.
Forget it, you don't seem to be able to understand my point, which is
that idle-GC just moves the moment the GC happens. Without it, GC is
pretty much guaranteed to slow down execution of the user's command.
So if occasionally the user hits a key during the idle-GC, he just gets
to experience the delay that he would otherwise *always* experience.
> timers kick in. As result, I needed to tune several long-running idle
> timers. I'd hate to see GC becoming one of them.
The purpose of the idle-GC is not to *add* more background activity, but
to move activity from active time to idle time. So if it works as
intended it is not comparable to those other long-running idle timers.
Stefan
next prev parent reply other threads:[~2020-04-10 14:34 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
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 [this message]
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=jwvk12nxvjr.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dim1212k@gmail.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 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.