Gnus development mailing list
 help / color / mirror / Atom feed
From: Norman Walsh <ndw@nwalsh.com>
To: ding@gnus.org
Subject: Trimming .gnus.registry.eieio?
Date: Tue, 19 Feb 2019 11:19:02 -0600	[thread overview]
Message-ID: <m2tvgz4ry1.fsf@nwalsh.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]

Hi all,

I noticed that my .gnus.registry.eieio file had grown to about 27M. I
noticed this because saving it was taking a distinctly noticable
amount of time.

The gnus registry setup page has two examples of
gnus-registry-max-entries, 2,500 and 50,000. I had mine set to 20,000.

I set it back to 2,500, started gnus, saved the file (and saw a message
about saving 2256 entries) and quit gnus.

My .gnus.registry.eieio file is now 21M.

I wonder if, perhaps, something has gone wrong. I suppose I could just
delete the registry file and let it start over, but I wonder if
there’s something less dramatic that I could do to trim it back.

And since I’m asking, of 2,500 and 50,000, which is the more
reasonable max entries size?

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | The Future is something which everyone
http://nwalsh.com/            | reaches at the rate of sixty minutes an
                              | hour, whatever he does, whoever he
                              | is.--C. S. Lewis

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

             reply	other threads:[~2019-02-19 17:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 17:19 Norman Walsh [this message]
2019-02-19 19:35 ` Eric Abrahamsen
2019-02-19 20:18   ` Norman Walsh
2019-02-20  1:13     ` Eric Abrahamsen
2019-02-20  7:39     ` Colin Baxter
2019-02-19 22:40   ` Michael Heerdegen
2019-02-20  1:06     ` Eric Abrahamsen
2019-02-20 15:16     ` Norman Walsh

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=m2tvgz4ry1.fsf@nwalsh.com \
    --to=ndw@nwalsh.com \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).