From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 40704@debbugs.gnu.org
Subject: bug#40704: 28.0.50; Improve and speed up (Gnus) registry saving
Date: Mon, 20 Apr 2020 20:42:21 -0700 [thread overview]
Message-ID: <87o8rl33oi.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87lfmpkac0.fsf@web.de> (Michael Heerdegen's message of "Tue, 21 Apr 2020 01:26:39 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> > Any comments on the suggested changes?
>>
>> Not that it's up to me,
>
> I wonder who it's up to...
There's sort of a `with-gnus-bug-report' macro that we're working with
here, where if Lars (or in this case, Ted Zlatanov) doesn't respond
within a certain period of time, the commit automatically goes in.
>> but I'm all for putting in #1 and #3 as-is, and adjusting #2 to scale
>> with the number of `gnus-registry-max-entries', with the addition of a
>> hard ceiling.
>
> Too large values of `gnus-registry-max-entries' can be harmful
> (fragmentation of memory?), I wonder if this can potentially be the case
> here.
Well that's where the hard ceiling comes in, right?
> I'm also not sure if scaling is a good idea at all. The value I chose
> will still make gc happen much less frequently even if your registry is
> huge. So it's still a win. If your value is too large, the final
> cleanup may take longer as necessary -- who has experience with this
> problem -- anybody?
Not me, let's hope for more respondents...
next prev parent reply other threads:[~2020-04-21 3:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 2:14 bug#40704: 28.0.50; Improve and speed up (Gnus) registry saving Michael Heerdegen
2020-04-20 4:13 ` Eric Abrahamsen
2020-04-20 23:26 ` Michael Heerdegen
2020-04-21 3:42 ` Eric Abrahamsen [this message]
2020-04-23 1:32 ` Michael Heerdegen
2020-04-23 2:36 ` Eric Abrahamsen
2020-04-29 16:11 ` Eric Abrahamsen
2020-07-19 2:16 ` Lars Ingebrigtsen
2020-07-19 14:52 ` Michael Heerdegen
2020-07-19 14:58 ` Lars Ingebrigtsen
2020-07-19 15:19 ` Michael Heerdegen
2020-07-19 15:22 ` Lars Ingebrigtsen
2020-07-19 15:23 ` Michael Heerdegen
2020-07-19 15:32 ` Lars Ingebrigtsen
2020-10-01 18:22 ` Lars Ingebrigtsen
2020-10-01 23:53 ` Michael Heerdegen
2020-10-02 1:38 ` Lars Ingebrigtsen
2022-04-17 15:21 ` Lars Ingebrigtsen
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=87o8rl33oi.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=40704@debbugs.gnu.org \
--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 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).