Deployment & Sizing Guide

Professional infrastructure planning for environments ranging from small labs to global enterprise deployments.

📊 Sizing Matrix 🏢 Deployment Tiers 💾 Storage Planning ⚡ Performance Tuning 📈 Scaling Path ✅ Deployment Checklist

Deployment Sizing Matrix

Categorized deployment requirements for optimal performance at any scale

Tier Device Count CPU (Cores) RAM Storage (NVMe SSD) Recommended DB Score
Entry 1 – 1,000 4 Cores 8 – 16 GB 256 GB SQLite (Embedded)
Pro 1,001 – 2,000 6 – 8 Cores 16 GB 512 GB SQLite / SQL Express
Business 2,001 – 5,000 8 – 12 Cores 32 GB 1 TB SQL Server / PostgreSQL
Enterprise 5,000+ 16+ Cores 64 GB+ 2 TB+ (RAID 10) SQL Server / PostgreSQL Cluster

Interactive Deployment Planner

Entry Tier

"Perfect for labs, admin workstations, and small branch offices."

Capacity
1 – 1,000 Devices
Processor
4 Cores
Memory
8 – 16 GB
Storage
256 GB NVMe
Network
1 Gbps NIC
Recommended Database Engine
SQLite (Embedded)
Technical Guidance

Focus on low footprint and ease of install. Single partition is fine. Standard 1 Gbps NIC sufficient. Perfect for running on a high-end admin laptop or a basic VM.

Use Case Examples
Development Labs Small Branch Offices IT Admin Workstations Evaluation Environments
Quick Cost Estimate
$2,500 - $4,000
Hardware investment range

Tier-Specific Technical Guidance

Detailed recommendations for each deployment tier

S

Entry Tier

1 – 1,000 Devices

Optimized for development, evaluation, or lab environments with minimal infrastructure requirements.

  • Single partition deployment
  • Standard 1 Gbps network interface
  • Perfect for admin laptops or basic VMs
  • Zero-config SQLite database
M

Pro Tier

1,001 – 2,000 Devices

Designed for reliable 24/7 background monitoring with dedicated resources for continuous operation.

  • Dedicated partition for database
  • Tune MaxParallelScans to ~100
  • Recommended for branch offices
  • Consider SQL Express for growth
L

Business Tier

2,001 – 5,000 Devices

Optimized for reporting performance and data retention in corporate environments.

  • Migrate to service-based database
  • Place server on core switch trunk
  • Handle concurrent UI and scan writes
  • Consider SQL Server or PostgreSQL
XL

Enterprise Tier

5,000+ Devices

High Availability (HA) architecture for massive I/O and mission-critical deployments.

  • Enterprise-grade NVMe storage
  • Offload database to separate server
  • Use 14.4 GB/day rule for sizing
  • Implement RAID 10 for redundancy

Storage Estimation & Planning

Calculate storage requirements based on your specific monitoring needs

Storage Calculation Formula

Stotal = (D × Eday × Zentry) × Rdays
D Number of Devices
Eday Entries per day (based on scan frequency)
Zentry Average entry size (~1 KB)
Rdays Retention period in days

Scan Frequency Examples

0
1-minute intervals
0
2-minute intervals
0
5-minute intervals

Example Calculation

10,000 Devices at 1-minute Intervals

10,000 × 1,440 × 1 KB = 0 GB/day
30-day retention: 14.4 GB × 30 = 0 GB
90-day retention: 14.4 GB × 90 = 0 TB

5,000 Devices at 5-minute Intervals

5,000 × 288 × 1 KB = 0 GB/day
30-day retention: 1.44 GB × 30 = 0 GB

Storage Recommendations

Storage Type Guidance

NVMe SSD
Recommended for all tiers
SATA SSD
Acceptable for Entry tier

Partition Strategy

Entry/Pro Tiers
Single partition acceptable
Business Tier
Separate OS and data drives
Enterprise Tier
Dedicated storage array with RAID

Retention Policy Examples

Development/Test 7 days
Production Monitoring 30 days
Compliance/Audit 90-365 days

Backup Recommendations

Daily snapshots RDBMS replication Off-site backup Point-in-time recovery

Performance Tuning & Optimization

Configuration recommendations for optimal performance at scale

Concurrency Management

Fine-tune MaxParallelScans and BatchSize based on host thread availability and network bandwidth.

Recommended Settings
Entry Tier: MaxParallelScans: 50-100
Pro Tier: MaxParallelScans: 100-200
Enterprise: MaxParallelScans: 300-500

I/O Optimization

Utilize DbFlushIntervalMs to batch database writes, reducing disk contention during heavy reporting.

Database Tuning
Default: DbFlushIntervalMs = 1000ms
High I/O: Increase to 5000ms
Aggregate writes for performance

Resource Cleanup

Automated purging of Temp directory following PDF generation to prevent disk exhaustion.

Maintenance Settings
Auto-purge Temp files: Enabled
Retention policy: Configurable
Secure deletion of temp data

High Availability Recommendations

Mission-Critical Deployments

Isolate Scanning Worker
Separate from UI Dashboard for independent scaling
Offload Database
Dedicated, redundant cluster for database operations

Disaster Recovery

Cold Start Testing
Regular database restoration validation
Automated Backups
Daily snapshots with retention policy

Need Custom Deployment Planning?

Our solutions architects can help design the optimal deployment for your specific environment and requirements.