MajwareMAJWARE
Free ToolNo SignupPACS · RIS · VNA

VM Sizing Calculator for PACS, RIS & VNA

Estimate vCPU, RAM, VM disks, IOPS and cluster hosts from your exam volume and user count. Add HA and performance buffers, project five years of growth against your cluster, and compare cloud with on-prem cost.

Runs in your browser, nothing is sent anywhere
Results update as you type
Every formula is shown below

Workload

Jump to results ↓
%

Components

Switch on what your PACS, RIS or VNA deployment runs. Open a component to change its sizing assumptions.

Sizing assumptions
vCPU
vCPU
GB
GB
GB
GB
Mbps
Sizing assumptions
vCPU
vCPU
GB
GB
GB
GB
Mbps
Sizing assumptions
vCPU
vCPU
GB
GB
GB
GB
Mbps
Sizing assumptions
vCPU
vCPU
GB
GB
GB
GB
Mbps
Sizing assumptions
vCPU
vCPU
GB
GB
GB
GB
Mbps
Sizing assumptions
vCPU
vCPU
GB
GB
GB
GB
Mbps
Sizing assumptions
vCPU
vCPU
GB
GB
GB
GB
Mbps

Resilience

%
%

Your cluster

The hosts you have today, used for host counts and saturation.

GB

Cost

$
$
$
$
%

Total vCPU

105

With buffers applied

Total RAM

234 GB

With buffers applied

VM disks

2,685 GB

OS and data disks, not the image archive

Total IOPS

15,038

With buffers applied

Hosts needed

1

2 with N+1 redundancy

Cluster saturates

Beyond Year 5

First year above 85% utilization

VM allocation

Sized per component, before HA and performance buffers. vCPU rounds up to multiples of 2, RAM to multiples of 4 GB.

Virtual machine allocation by component
ComponentvCPURAM GBOS disk GBData disk GBIOPSNetwork Mbps
Application Server1428120501,0001,000
Database Server18521205004,0001,000
Web Server81612020450500
Broker / Integration81612030675500
DICOM Server14281202003,0002,000
AI Module (off)0012010002,000
Reporting Server81612050900500
Total7015684095010,0257,500

Components switched off add no vCPU, RAM or IOPS, but their disk and network figures still count toward the totals. Set them to 0 under Sizing assumptions to remove them.

From base to final sizing

Resources before and after high availability and performance buffers
ResourceBaseWith HAWith performance buffer
vCPU7088105
RAM (GB)156195234
VM disks (GB)1,7902,2382,685
IOPS10,02512,53115,038

Hosts needed: 1 by vCPU and 1 by RAM, using the larger. That works out at 105 vCPU and 234 GB RAM per host.

5-year growth against your cluster

Your cluster has 512 vCPU and 2,048 GB RAM. Year 0 is today.

vCPU utilizationRAM utilization
Projected resources and utilization by year
YearExamsvCPURAM GBVM disks GBIOPSvCPU useRAM use
Year 0250,0001052342,68515,03820.5%11.4%
Year 1275,0001162572,95416,54122.6%12.6%
Year 2302,5001272833,24918,19524.8%13.8%
Year 3332,7501403113,57420,01527.3%15.2%
Year 4366,0251543433,93122,01630.0%16.7%
Year 5402,6281693774,32424,21833.0%18.4%

First year above 85%: vCPU Beyond Year 5, RAM Beyond Year 5.

5-year cost: cloud and on-prem

Cloud cost estimate
CloudCost
vCPU / month$3,150
RAM / month$1,170
VM disks / month$210
Total / month$4,530
Total / year$54,357
5-year cost$271,786
On-prem cost estimate
On-premCost
1 host$25,000
Maintenance / year$4,500
5-year cost$47,500

On-prem cost is priced on the 1 host needed for capacity, before N+1. With N+1 you would buy 2.

Cloud covers vCPU, RAM and VM disks. On-prem covers hosts and maintenance. Licensing, power, staff and the image archive are not included in either.

Performance buffer comparison

The base totals at different buffers, without HA overhead.

%
Base totals at different performance buffers
ResourceNo buffer10%20%Custom (15%)
vCPU70778481
RAM (GB)156172187179
IOPS10,02511,02812,03011,529

Sizing the image archive as well? Use the PACS Storage Growth Calculator.

How the numbers are calculated

Sizing runs per component, and each component rounds up before the totals are added. The buffers then apply to the totals.

Base demand, per component
base + (annual exams ÷ 100,000) × per-100k figure
vCPU adjustments
base vCPU × (1 + concurrent users ÷ 100), × 1.25 for the database above 500,000 exams
Distributed deployments
vCPU, RAM and IOPS × sites connected
Final sizing
component totals × (1 + failover buffer, when HA is on) × (1 + performance buffer)
Hosts needed
the larger of final vCPU ÷ vCPU per host and final RAM ÷ RAM per host, rounded up
Growth and saturation
final × (1 + growth)^year ÷ (per-host capacity × hosts available), saturated above 85%
Cloud 5-year cost
((vCPU × rate) + (RAM × rate) + (disk TB × rate)) × 12 × 5
On-prem 5-year cost
(hosts × cost per host) + 5 × (maintenance % × hosts × cost per host)

Common questions

Does this work for PACS, RIS and VNA?

Yes, as a starting estimate. The calculator sizes seven common server roles from your exam volume and user count, and you switch off the roles your system does not run. It is not specific to any vendor, so edit the sizing assumptions to match your vendor's published figures.

How is each virtual machine sized?

Each component starts from a base figure plus an amount per 100,000 exams. vCPU then scales with concurrent users, the database server takes an extra 25% above 500,000 exams, and distributed deployments multiply vCPU, RAM and IOPS by the site count. vCPU rounds up to multiples of 2 and RAM to multiples of 4 GB.

Does the storage figure include my images?

No. It covers the OS and data disks on the virtual machines only. Size the image archive separately with the PACS Storage Growth Calculator.

How is the host count worked out?

The final vCPU and RAM totals are divided by the capacity of one host and rounded up, and the larger result is used. With high availability on, N+1 adds one more host. On-prem cost is priced on the count before N+1, so add one host to your budget if you plan to run N+1.

What does cluster saturation mean here?

Saturation is the first year projected vCPU or RAM goes above 85% of your cluster capacity, using your annual growth rate. Year 0 is today, so "Now" means the cluster is already over the line.

Can I use this instead of vendor sizing?

No. Use it to frame the conversation and to check a vendor sheet for gaps. Final specifications need validating against your vendor and platform, and against measured peak load once the system is live.

This calculator gives planning estimates and does not replace vendor sizing documents or a formal architecture review. Check final specifications against your vendor and platform requirements.