Problem with C++ wrapper and gpgme

[David Shaw]

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

On Mon, Jun 02, 2003 at 10:06:23PM +0400, Yenot wrote:
> On Monday 02 June 2003 05:08 pm, David Shaw wrote:
> > On Mon, Jun 02, 2003 at 11:01:22AM +0400, Yenot wrote:
> > > On Monday 02 June 2003 05:06 am, David Shaw wrote:
> > > > On Mon, Jun 02, 2003 at 02:40:21AM +0400, Yenot wrote:
> > > [...]
> > > > > On my notebook with 568 keys, I get the following results:
> > > [...]
> > > > > % /usr/bin/time -p gpg --fixed-list-mode --with-colons
> > > > > --list-keys --with-fingerprint --with-fingerprint > /dev/null
> > > > > real 44.28
> > > > > user 37.17
> > > > > sys 2.08
> > > [...]
> > > > That's way, way too long.  Can you do a "gpg
> > > > --rebuild-keydb-cache" and try again?
> > >
> > > It cut the time in half.  I did run "--rebuild-keydb-cache" after
> > > upgrading to 1.0.7 (a long time ago).
> >
> > Good.  Do you still have a copy of 1.2.1 around?  Can you do the
> > check with that?  1.2.2 has a bug that makes key listings slow.
> 
> The combination of the older GnuPG and the rebuild of the keydb is 
> yielding much better results:
>  real 0.28
>  user 0.25
>  sys 0.02

Ok, perfect.  So, to get back to the original comment: if things are
this fast, there is little need for using raw data between GnuPG and a
key manager application.

When 1.2.3 is released, it will include a fix for the key listing
slowdown.

David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3-cvs (GNU/Linux)
Comment: Key available at http://www.jabberwocky.com/david/keys.asc

iD8DBQE+25654mZch0nhy8kRAtbXAJ4qCYgY1bNPERDQiq8Dp3qPQuBbpACgvQSt
0WaMUtgVRk4Bl1iCAYcqZP8=
=U56z
-----END PGP SIGNATURE-----