Large keyrings, GnuPG slowdowns/Seahorse segfaults

[Shawn K. Quinn]

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

My apologies if this is too far off topic, but there doesn't appear to=20
be a Seahorse-specific mailing list.

Up until a few minutes ago (when I realized this was slowing down even=20
standalone operation of GnuPG greatly) I had a >11 megabyte public=20
keyring. This caused Seahorse to segfault after about a couple of=20
minutes. I was mainly just curious if anyone else had experienced=20
similar behavior from Seahorse?

I was also wondering where, if anywhere, on the priority list were=20
optimizations for users with large keyrings. I realize average users=20
will have keyrings of maybe 2 megabytes max, but shouldn't there should=20
be some way of keeping things from becoming dog slow with large=20
keyrings?

- --=20
Shawn K. Quinn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9hErUQVXDBVmaIp0RAtjDAJ4p5d9sMeIpey5eTIQP+k511lwRagCgg76s
cDbb+bnC2VuPOyAaTY2cEuo=3D
=3Dl5wL
-----END PGP SIGNATURE-----