From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, 37321@debbugs.gnu.org
Subject: bug#37321: 27.0.50; Excessive gc in a use case (el-search)
Date: Tue, 08 Oct 2019 13:12:29 +0200 [thread overview]
Message-ID: <87pnj7xzhe.fsf@web.de> (raw)
In-Reply-To: <83k19fy4p7.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 08 Oct 2019 12:19:48 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Start with 4 times the default. If that's not enough, double the
> value until you are satisfied, and tell what was the final value.
I leave it to you to interpret the result (can we expect that other use
cases have a similar optimum?):
My current setup (setq gc-cons-percentage .8)
52.331413s (7.141519s in 20 GCs)
Default: (setq gc-cons-threshold 800000)
87.626289s (41.526705s in 269 GCs)
(setq gc-cons-threshold (* 800000 2))
86.213154s (40.132441s in 267 GCs)
(setq gc-cons-threshold (* 800000 4))
87.422085s (40.967298s in 267 GCs)
(setq gc-cons-threshold (* 800000 8))
84.519948s (38.535352s in 245 GCs)
(setq gc-cons-threshold (* 800000 16))
81.596529s (34.603730s in 193 GCs)
(setq gc-cons-threshold (* 800000 32))
70.866717s (24.850518s in 123 GCs)
(setq gc-cons-threshold (* 800000 64))
61.893515s (14.088496s in 63 GCs)
(setq gc-cons-threshold (* 800000 128))
56.277259s (8.122554s in 32 GCs)
(setq gc-cons-threshold (* 800000 256))
55.173263s (6.067774s in 17 GCs)
(setq gc-cons-threshold (* 800000 512))
56.116736s (8.825274s in 9 GCs)
(setq gc-cons-threshold (* 800000 1024))
70.832969s (19.474471s in 5 GCs)
Regards,
Michael.
next prev parent reply other threads:[~2019-10-08 11:12 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
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 [this message]
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
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=87pnj7xzhe.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=37321@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@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).