<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=215880) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=215880) </details> <!--IssueSummary end--> As referenced in https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/259#note_330564176. The concern is that [using_tmp_keychain](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/gpg.rb#L76) is single-threaded and this may be causing the create_commit_signature worker to saturate its queue. This issue is intended to explore the possibility of getting rid of the `GPGME` dependency. @nick.thomas [has suggested that](https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/259#note_331942710) https://godoc.org/golang.org/x/crypto/openpgp may be enough to perform the operations needed.