A modest server is plenty

On just 2 CPUs and 2 GiB RAM, Telebugs stored a burst of 1,000 reports in 13.4 seconds in our benchmark. One container, without demanding an infrastructure team.

Published benchmark (median of five runs)
---------------------------------
EnvironmentNative AMD64 Linux VM
App limits2 CPUs / 2 GiB RAM
WorkloadBurst of 1,000 reports / 4 connections

Stored reports1,000 / 1,000
Completed in13.4 seconds
Completed throughput74.9 reports/s

How modest are we talking?

You can start with just 1 CPU core, 1 GB of RAM, and 40 GB of disk. For a busier setup, 2 cores and 4 GB of RAM give Telebugs more room to breathe. Our benchmark limited the application container to 2 CPUs and 2 GiB of RAM.

What does 75 reports a second measure?

We sent a burst of 1,000 reports over four connections and timed it until every report was stored and the queue was empty. The median of five runs was 13.4 seconds, or 74.9 stored reports per second. This measures a fixed burst, not a sustained capacity limit. External notifications were not configured. You can see the whole benchmark.

Will every workload fit?

No, and they do not have to. Error volume, retention, release artifacts, and how many projects share the server all add weight. Start small. If Telebugs needs more room later, move it to a bigger server. Your apps will not know the difference.

What about ARM?

It works there too. Telebugs supports AMD64 and ARM64. An ARM cloud server or Raspberry Pi-class machine is fine, as long as it has enough RAM and disk for the amount of error data you keep.