From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: michael_heerdegen@web.de, 37321@debbugs.gnu.org
Subject: bug#37321: 27.0.50; Excessive gc in a use case (el-search)
Date: Sat, 14 Sep 2019 12:57:49 +0300 [thread overview]
Message-ID: <838sqryzc2.fsf@gnu.org> (raw)
In-Reply-To: <b37e7fc9-c8b3-0b7f-d72a-435ae92355b5@cs.ucla.edu> (message from Paul Eggert on Sat, 14 Sep 2019 01:52:27 -0700)
> Cc: michael_heerdegen@web.de, 37321@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sat, 14 Sep 2019 01:52:27 -0700
>
> On 9/14/19 1:37 AM, Eli Zaretskii wrote:
> > It might be a good
> > idea to give users who do care some inside information to allow them
> > to tune their GC tricks to these changes -- it could lower the number
> > of bug reports that I'm afraid will follow.
>
> I could add something to NEWS along the lines of "The heuristics for when to
> garbage collect have been tweaked, in an attempt to make Emacs perform a bit
> better and follow its documentation a bit more closely." Dunno how much that
> would help, though. It'd be hard to be much more specific.
If we cannot give any specifics, I think at least telling users to
re-tune their GC tricks would help.
Thanks.
next prev parent reply other threads:[~2019-09-14 9:57 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 13:52 bug#37321: 27.0.50; Excessive gc in a use case (el-search) Michael Heerdegen
2019-09-07 14:23 ` Michael Heerdegen
2019-09-07 15:30 ` Michael Heerdegen
2019-09-08 1:11 ` Paul Eggert
2019-09-08 14:52 ` Michael Heerdegen
2019-09-08 15:25 ` Michael Heerdegen
2019-09-14 8:04 ` Paul Eggert
2019-09-14 8:37 ` Eli Zaretskii
2019-09-14 8:52 ` Paul Eggert
2019-09-14 9:57 ` Eli Zaretskii [this message]
2019-09-14 17:57 ` Paul Eggert
2019-09-14 18:16 ` Eli Zaretskii
2019-09-15 4:33 ` Richard Stallman
2019-09-16 23:53 ` Michael Heerdegen
2019-09-17 0:55 ` Paul Eggert
2019-09-21 0:41 ` Michael Heerdegen
2019-09-21 0:46 ` Michael Heerdegen
2019-09-21 6:19 ` Paul Eggert
2019-09-17 12:47 ` Noam Postavsky
2019-09-21 0:44 ` Michael Heerdegen
2019-09-25 9:42 ` Michael Heerdegen
2019-09-25 20:37 ` Paul Eggert
2019-09-26 11:42 ` Michael Heerdegen
2019-09-26 12:14 ` Eli Zaretskii
2019-09-26 13:03 ` Michael Heerdegen
2019-10-08 8:43 ` Michael Heerdegen
2019-10-08 9:09 ` Eli Zaretskii
2019-10-08 9:11 ` Michael Heerdegen
2019-10-08 9:19 ` Eli Zaretskii
2019-10-08 11:12 ` Michael Heerdegen
2019-10-08 12:11 ` Eli Zaretskii
2019-10-08 12:38 ` Michael Heerdegen
2019-10-08 13:03 ` Eli Zaretskii
2019-10-09 14:47 ` Michael Heerdegen
2019-10-09 15:33 ` Eli Zaretskii
2019-10-09 20:53 ` Paul Eggert
2019-10-10 10:58 ` Michael Heerdegen
2019-10-08 9:22 ` Michael Heerdegen
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=838sqryzc2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37321@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=michael_heerdegen@web.de \
/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.