Large keyrings, GnuPG slowdowns/Seahorse segfaults

[Ingo Klöcker]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 15 September 2002 10:54, Shawn K. Quinn wrote:
> I was also wondering where, if anywhere, on the priority list were
> optimizations for users with large keyrings. I realize average users
> will have keyrings of maybe 2 megabytes max, but shouldn't there
> should be some way of keeping things from becoming dog slow with
> large keyrings?

You should try if running 'gpg --rebuild-keydb-caches' helps. I just ran 
it again yesterday and the time needed for a run of 'gpg 
- --check-trustdb' went down from about 10 seconds to about 1 second.

BTW, why is this command neither listed in the manual page nor in the 
output of 'gpg --help'?

Regards,
Ingo

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9hGdSGnR+RTDgudgRAvlKAJ4/r5drtE6nhls1WvDFG6KLj3SB5QCeNKM5
zYywyXtnRX8rQLkOPNvCx2U=
=/u0V
-----END PGP SIGNATURE-----