---
title: "Discussion on \"How We Cut CertPulse's Scan Time From 47 Minutes to 90 Seconds: A Concurrency Postmortem\" | Hashnode"
description: "Discussion on \"How We Cut CertPulse's Scan Time From 47 Minutes to 90 Seconds: A Concurrency Postmortem\". The architectural decisions, dead ends, and goroutine pool tuning that took our multi-cloud certificate scanner from unusable to fast."
url: "https://hashnode.com/posts/how-we-cut-certpulses-scan-time-from-47-minutes-to-90-seconds-a-concurrency-postmortem/69f8708fb25502e6a1c9e674"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How We Cut CertPulse's Scan Time From 47 Minutes to 90 Seconds: A Concurrency Postmortem](https://certpulse.hashnode.dev/how-we-cut-certpulses-scan-time-from-47-minutes-to-90-seconds-a-concurrency-postmortem?utm_source=hashnode&utm_medium=feed)

The architectural decisions, dead ends, and goroutine pool tuning that took our multi-cloud certificate scanner from unusable to fast.

May 4 · 10 min read · certpulse.hashnode.dev  
Read the article

-   [#certpulse](https://hashnode.com/tag/certpulse)
-   [#build-in-public](https://hashnode.com/tag/build-in-public)
-   [#concurrency](https://hashnode.com/tag/concurrency)
-   [#go](https://hashnode.com/tag/go)
-   [#performance](https://hashnode.com/tag/performance)

## Written by

[nine](https://hashnode.com/@xdsai)

@xdsai

  
[View profile](https://hashnode.com/@xdsai)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
