Sizing step-ca Resources for High-Throughput Certificate Issuance

[jaingeet]

We are deploying step-ca using the official Helm charts and anticipate a consistent certificate issuance rate of approximately 100 QPS per step-ca instance.

What are some reasonable initial CPU and Memory resource requests and limits to configure in our Helm chart values for the step-ca pods to adequately support this throughput? We understand this can vary, but we're looking for general guidance or rules of thumb based on typical workloads.

Given that we are using a PostgreSQL database for step-ca, how can we estimate the storage space needed per issued certificate and per revocation record? We need to factor this into our persistent volume sizing for the PostgreSQL database.

[tashian]

Good question. Right now we don't have any guidance on capacity planning for large step-ca installations. We're a small team with a lot of priorities, and we don't currently have the bandwidth to do the load testing that would be required to gather this information.

[jaingeet]

I see. Does the smallstep/certificates library offer any built-in tools or features to facilitate load testing of a step-ca deployment?