gpg verification slows down my gnus

gpg verification slows down my gnus

[news]

gpg verification is slowing down my oort gnus:

Function Name                  Call Count  Elapsed Time  Average Time
=============================  ==========  ============  ============
gpg-verify                     1           16.663583     16.663583
gpg-with-temp-files-create     1           0.03351       0.03351
gpg-make-temp-file             2           0.033345      0.0166725
gpg-with-temp-files-delete     1           0.000525      0.000525
gpg-build-arg-list             1           6.4e-05       6.4e-05
gpg-exec-path                  1           1.8e-05       1.8e-05

gpg is byte compiled.  What can I do to speed this up?

Chris

Re: gpg verification slows down my gnus

[Simon Josefsson]

On Fri, 14 Jun 2002 news@kippona.com wrote:

> gpg verification is slowing down my oort gnus:

Don't enable it then. :-)

> Function Name                  Call Count  Elapsed Time  Average Time
> =============================  ==========  ============  ============
> gpg-verify                     1           16.663583     16.663583
> gpg-with-temp-files-create     1           0.03351       0.03351
> gpg-make-temp-file             2           0.033345      0.0166725
> gpg-with-temp-files-delete     1           0.000525      0.000525
> gpg-build-arg-list             1           6.4e-05       6.4e-05
> gpg-exec-path                  1           1.8e-05       1.8e-05
> 
> gpg is byte compiled.  What can I do to speed this up?

The time is probably spent in the external "gpg" application, most likely
trying to retrieve keys from a keyserver.  The elisp processing required
is minimal.

Asynchronous security verification would be quite useful.  Patches, 
anyone? :-)

Re: gpg verification slows down my gnus

[Chris Beggy]

On 14 Jun 2002, Simon Josefsson <jas@extundo.com> wrote: 

> On Fri, 14 Jun 2002 news@kippona.com wrote:
> 
> > gpg verification is slowing down my oort gnus:
> 
> Don't enable it then. :-)

Thanks for replying.

> > Function Name                  Call Count  Elapsed Time  Average Time
> > =============================  ==========  ============  ============
> > gpg-verify                     1           16.663583     16.663583
> > gpg-with-temp-files-create     1           0.03351       0.03351
> > gpg-make-temp-file             2           0.033345      0.0166725
> > gpg-with-temp-files-delete     1           0.000525      0.000525
> > gpg-build-arg-list             1           6.4e-05       6.4e-05
> > gpg-exec-path                  1           1.8e-05       1.8e-05
> > 
> > gpg is byte compiled.  What can I do to speed this up?
> 
> The time is probably spent in the external "gpg" application, most likely
> trying to retrieve keys from a keyserver.  The elisp processing required
> is minimal.

This profile was for a verification of a key on my keyring.  Does
gpg go and fetch before it checks the local keyring?

> Asynchronous security verification would be quite useful.  Patches, 
> anyone? :-)

mew seems to do this, somehow checking sigs after the mail is
read in from the spool and while it is being summarized.
Then, I think it caches the result (verified, not verified, key
unreachable) for a time, so that re-reads don't generate new gpg
verification calls.

For comparison, I tried to write out the message from gnus (X O)
and then run gpg on the command line, gpg --verify
message.txt. This wouldn't complete.

What's the right way to do that?

Chris

Re: gpg verification slows down my gnus

[Simon Josefsson]

Chris Beggy <chrisb@kippona.com> writes:

>> > Function Name                  Call Count  Elapsed Time  Average Time
>> > =============================  ==========  ============  ============
>> > gpg-verify                     1           16.663583     16.663583
>> > gpg-with-temp-files-create     1           0.03351       0.03351
>> > gpg-make-temp-file             2           0.033345      0.0166725
>> > gpg-with-temp-files-delete     1           0.000525      0.000525
>> > gpg-build-arg-list             1           6.4e-05       6.4e-05
>> > gpg-exec-path                  1           1.8e-05       1.8e-05
>> > 
>> > gpg is byte compiled.  What can I do to speed this up?
>> 
>> The time is probably spent in the external "gpg" application, most likely
>> trying to retrieve keys from a keyserver.  The elisp processing required
>> is minimal.
>
> This profile was for a verification of a key on my keyring.  Does
> gpg go and fetch before it checks the local keyring?

I guess not.  Do you have a large keyring?  I find gpg becomes slow if
the keyring is large.

>> Asynchronous security verification would be quite useful.  Patches, 
>> anyone? :-)
>
> mew seems to do this, somehow checking sigs after the mail is
> read in from the spool and while it is being summarized.
> Then, I think it caches the result (verified, not verified, key
> unreachable) for a time, so that re-reads don't generate new gpg
> verification calls.

That could work, altough you might end up with stale data.

> For comparison, I tried to write out the message from gnus (X O)
> and then run gpg on the command line, gpg --verify
> message.txt. This wouldn't complete.
>
> What's the right way to do that?

Another way would be to simply display the message immediately, and
launch gpg in the background.  When gpg finishes, the article buffer
is updated with the information.

Re: gpg verification slows down my gnus

[news]

Simon Josefsson <jas@extundo.com> writes:

> I guess not.  Do you have a large keyring?  I find gpg becomes slow if
> the keyring is large.

Thanks for your response.

My pubring.gpg is about 600K bytes.  Is that large?  I'm also part
of a web-of-trust:

  http://www.phillylinux.org/keys/

which may also be a factor slowing things down.

Upgrading from gpg 1.0.4 to 1.0.7 sped things up tremendously.

Chris

Re: gpg verification slows down my gnus

[Alan Shutko]

news@kippona.com (Chris Beggy ) writes:

> Upgrading from gpg 1.0.4 to 1.0.7 sped things up tremendously.

If you haven't done it yet, try gpg --rebuild-keydb-caches

-- 
Alan Shutko <ats@acm.org> - In a variety of flavors!
People who go to conferences are the ones who shouldn't.

Re: gpg verification slows down my gnus

[news]

Alan Shutko <ats@acm.org> writes:

> news@kippona.com (Chris Beggy ) writes:
>
>> Upgrading from gpg 1.0.4 to 1.0.7 sped things up tremendously.
>
> If you haven't done it yet, try gpg --rebuild-keydb-caches

Done.  Where do the caches live?  In RAM?

Chris

Re: gpg verification slows down my gnus

[Florian Weimer]

(Chris Beggy ) news@kippona.com writes:

> What can I do to speed this up?

Which GnuPG version are you using?

Re: gpg verification slows down my gnus

[news]

Florian Weimer <fw@deneb.enyo.de> writes:

> (Chris Beggy ) news@kippona.com writes:
>
>> What can I do to speed this up?
>
> Which GnuPG version are you using?

gpg 1.0.4

Chris

Re: gpg verification slows down my gnus

[news]

(Chris Beggy ) news@kippona.com writes:

> Florian Weimer <fw@deneb.enyo.de> writes:
>
>> Which GnuPG version are you using?
>
> gpg 1.0.4

I took the hint, compiled and installed gnupg 1.0.7 and found
tremendous improvement, for the same signer, same keyring:

Function Name                  Call Count  Elapsed Time  Average Time
=============================  ==========  ============  ============
gpg-verify                     1           0.845249      0.845249
gpg-with-temp-files-create     1           0.035467      0.035467
gpg-make-temp-file             2           0.035334      0.017667
gpg-with-temp-files-delete     1           0.000451      0.000451
gpg-build-arg-list             1           5.9e-05       5.9e-05
gpg-exec-path                  1           1.5e-05       1.5e-05

Thanks for this suggestion.

Chris