unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Richard Stallman <rms@gnu.org>
Cc: 13795@debbugs.gnu.org
Subject: bug#13795: 24.3.50; epa-insert-keys improvements
Date: Mon, 07 Dec 2020 16:11:26 +0100	[thread overview]
Message-ID: <87y2i9hcrl.fsf@gnus.org> (raw)
In-Reply-To: <E1km9VW-0004pj-SL@fencepost.gnu.org> (Richard Stallman's message of "Mon, 07 Dec 2020 00:56:22 -0500")

Richard Stallman <rms@gnu.org> writes:

> I am running master from June.  epa-insert-keys just took 6 seconds
> to insert 700 keys.  I still have a build of master from Oct 2019;
> epa-insert-keys took the same time in that version.

Yes, that sounds uncomfortably slow.

Hm...  is there any way to inject hundreds of keys into the key ring to
make it easier to test what part of this is taking time.  Anybody know?

If it's external (i.e., the gpg tools are slow), then we should cache
the results -- otherwise we should fix the code on the Emacs side to be
faster.

> It could save the text in a file, and compare that file's mtime with
> that of the keyring to see whether to regenerate the file.  That way,
> the memoization will work from one Emacs session to another.

I think caching the data in a file would be more bother than it's worth,
but we could certainly cache the data in-memory during an Emacs session.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-12-07 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-23 18:57 bug#13795: 24.3.50; epa-insert-keys improvements Richard Stallman
2020-12-06 19:07 ` Lars Ingebrigtsen
2020-12-07  5:56   ` Richard Stallman
2020-12-07  5:56   ` Richard Stallman
2020-12-07 15:11     ` Lars Ingebrigtsen [this message]
2020-12-08  5:35       ` Richard Stallman

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=87y2i9hcrl.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=13795@debbugs.gnu.org \
    --cc=rms@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).