CubeAPM
CubeAPM CubeAPM

CubeAPM Infrastructure Sizing Calculator

Infrastructure Sizing

How much infrastructure does CubeAPM need?

Estimate the CPU, RAM, and disk required to run CubeAPM for your traces and logs ingestion volumes.

Data ingestion volume
Your Ingestion Volume
Enter your monthly volume per signal and choose how long you want to retain each.
TB/mo
TB/mo
Total monthly ingest
Tip: Enter your monthly ingestion volume per signal in TB. Each signal can have its own retention window — common defaults are 7 days for traces and logs.
Recommended Infrastructure
Three columns: Min (tight, real-world usage) · Recommended (with headroom) · Max (spike + growth buffer).
Ready to estimate
Enter your monthly ingestion volumes on the left, then click Estimate Infrastructure Requirements to see the recommended CPU, RAM, and disk.
CPU cores
9 + 0.161·traces + 0.111·logs (TB/mo)
Min
cores
Max
cores
RAM
10 + 1.277·traces + 0.968·logs (TB/mo)
Min
GB
Max
GB
Disk
Engineering formula: 96% compression × per-signal retention
Min
GB
Max
GB
Disk usage by signal (recommended)
Traces
Logs
How this is calculated: CPU and RAM coefficients come from a per-signal linear regression fit to 38 production customers, selected via leave-one-out cross-validation across 10 candidate models. Test MAPE: CPU 34% / RAM 38% (R² 0.74 / 0.88). Disk uses (TB/mo ÷ 30) × 0.04 × retention per signal — 96% compression — plus safety margin. Min/Max are ±30%/+50% of recommended for spike + growth headroom.

Want a real sizing recommendation?

Talk to our engineers — we'll review your workload and give you exact node counts, instance types, and storage tier guidance.

×
×