Page MenuHome GnuPG

gpgconf: Analyze timing on Windows
Open, NormalPublic

Description

During startup Kleopatra needs to very early get information about GnuPG configuration before showing UI. Half a second for this seems to be excessive at first glance. Although we should probably define the Test hardware we run on. We should investigate where this takes most time and if we see possibilities to optimize this.

In Powershell:

Measure-Command {gpgconf --list-options gpg ; gpgconf --list-options gpgsm ; gpgconf --list-options gpg-agent ; gpgconf --list-options scdaemon ; gpgconf --list-options dirmngr ; gpgconf --list-options pinentry}


Days              : 0
Hours             : 0
Minutes           : 0
Seconds           : 0
Milliseconds      : 413
Ticks             : 4137875
TotalDays         : 4,78920717592593E-06
TotalHours        : 0,000114940972222222
TotalMinutes      : 0,00689645833333333
TotalSeconds      : 0,4137875
TotalMilliseconds : 413,7875

Related Objects

Event Timeline

aheinecke triaged this task as Normal priority.Oct 27 2022, 10:54 AM
aheinecke created this task.

Would running the different --list-options in parallel make sense? Or would the block each other?

Alternatively, maybe a gpgconf --list-all-options (or --list-options all?) would be faster. Obviously, the listed options would have to be prefixed with the component name. Or we need a component header (like the group headers). Starting processes has been very slow on Windows so starting a single gpgconf instead of one per component could make a difference.