Page MenuHome GnuPG
Feed Advanced Search

Nov 18 2020

andrey.arapov added a comment to T5137: gpg-agent 2.x poor performance / futex errors.

Note that you actually run 30 independent processes with gpg 1.4 but with gpg-agent there is just one process to handle the private key operations (decrypt). To utilize more cores you need to setup several GNUPGHOME with the same private keys.

Nov 18 2020, 2:33 PM · Feature Request, gpgagent
andrey.arapov added a comment to T5137: gpg-agent 2.x poor performance / futex errors.

I think that it is not gpg-agent but pinentry which causes millions of futex syscall errors.
For interactive use case, pinentry may be the point of contention.
I might be wrong if your key is not protected by passphrase.

If possible, please try adding arguments for gpg invocation: --pinentry-mode loopback --passphrase-file YOUR_FILE_FOR_PASSPHRASE
This can avoid the invocation of pinentry entirely.

Nov 18 2020, 2:32 PM · Feature Request, gpgagent

Nov 16 2020

andrey.arapov created T5137: gpg-agent 2.x poor performance / futex errors.
Nov 16 2020, 4:34 PM · Feature Request, gpgagent