Sizing Guide

Size your RegScale deployment by component and by the tier that matches your performance and availability needs. A RegScale instance has two core components to size:

📘

Recommended sizing depends on your actual RegScale usage

The figures below are starting points, not fixed requirements. Real-world resource needs vary with how RegScale is used — the number of concurrent users, the volume of data and records under management, the number and frequency of integrations and scan imports, and reporting and automation workloads. Treat these tiers as a baseline, monitor utilization after go-live, and scale compute, memory, and database throughput up or down to match observed demand.

Sizing Tiers

TierUse For
MinimumEvaluation and non-production environments.
RecommendedStandard production deployments.
Production (HA)High-availability and high-throughput production workloads.

Compute Requirements

ComponentMinimumRecommendedProduction (HA)
Web / Application Server2 vCPU, 4 GB RAM4 vCPU, 8 GB RAM2+ nodes @ 4 vCPU, 8 GB RAM each; scale up or down as needed based on actual usage metrics
Database Server4 vCPU, 16 GB RAM8 vCPU, 32 GB RAMScale up or down as needed based on actual usage metrics; ensure database backups are enabled

📘

Run the application and database on separate hosts for any environment beyond evaluation.

Database Network

For the database tier, provision a low-latency network path between the application and database:

  • Place the application and database servers on the same low-latency network or region.
  • For Production (HA), enable database replication and run the application tier across multiple nodes.

Related