Package: gnupg Version: 2.1.16-3 Severity: normal Feature request.
When using gpg as invoked by duplicity, gpg is a main bottlneck. gpg is using 100% of single CPU core, and not any more. Utilizing more cores would speed up backups as done by duplicity, especially full backups by a factor of 10 on modern machines. Using cipher and compression algorithms that can utilize multiple cores (possibly at the expense of using more memory for buffers) would help a lot. Thanks. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-1-amd64 (SMP w/12 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnupg depends on: ii gnupg-agent 2.1.16-3 ii libassuan0 2.4.3-2 ii libbz2-1.0 1.0.6-8 ii libc6 2.24-8 ii libgcrypt20 1.7.5-2 ii libgpg-error0 1.25-2 ii libksba8 1.3.5-2 ii libreadline7 7.0-1 ii libsqlite3-0 3.15.2-1 ii zlib1g 1:1.2.8.dfsg-4 Versions of packages gnupg recommends: ii dirmngr 2.1.16-3 ii gnupg-l10n 2.1.16-3 Versions of packages gnupg suggests: pn parcimonie <none> pn xloadimage <none> -- no debconf information
