Last updated: 2026-11-06
Purpose
This article explains how to calculate and allocate CPU and memory resources to vertically scale an RC-Scanner for expected concurrent security scan workloads.
Introduction
Vertical scaling increases the scanning capacity of a single RC Scanner by adding CPU and memory resources. It provides an alternative to horizontal scaling, where additional RC-Scanners are deployed.
Use vertical scaling to increase the number of concurrent scans that an RC-Scanner can handle. Understanding the resource requirements for each scan type helps optimize scanner capacity and allocate sufficient resources for the expected workload.
Recommended Settings
The recommended settings for an RC Scanner depends on what type of workload will run on it, since different scan types are scaling differently. The following describes the recommended setting if you are purely using one type of scan product from Outpost24
|
Product |
NetSec |
Scale |
|---|---|---|
|
CPU |
8 |
8 |
|
RAM |
16 |
24 |
|
Disk |
30 |
30 |
With these settings, you are likely to see 8 to 9 scans running in parallel.
Scaling up CPU or RAM independently of the other is unlikely to yield significant or any result because. Scaling needs to happen according to the scaling formula below
Scaling Formula
RC Scanners are allocating scans according to a three step process
-
How much resources is available
-
How much is already consumed by running scans
-
How much does the next queued scan consume
If the queued scan would fit into the RC Scanner, it will be sent and scanned. This means that when scaling the resources, the resources that are currently a bottleneck is what needs to be scaled.
The RC Scanner also has some services required for its function, which is subtracted from the available resources. The currently baseline is 1C and 2GB. Subtract this from your deployed resources, and then calculate how much you can fit in parallel based on the scan types below,
|
Scan types |
CPU |
RAM |
|---|---|---|
|
Network Assessment |
0.5C |
1.1GB |
|
Application Assessment |
0.6C |
2GB |
|
Application Assessment + Infrastructure Scan |
1C |
1.4GB |
|
Network Discovery |
0.1C |
~100MB |
Example
Netsec Scanner
For example, if you want to run 12 network host assessments in parallel, this would consume the following resources:
|
|
CPU |
RAM |
|---|---|---|
|
Baseline |
1C |
2GB |
|
12 x Network Host Assessment |
6C |
13.2GB |
|
Total |
7C |
15.2GB |
This would fit into the recommended settings for a pure NetSec customer as shown below
|
|
CPU |
RAM |
|---|---|---|
|
Recommended |
8C |
16GB |
|
Consumed |
7C |
15.2GB |
|
Remaining |
1C |
0.8GB |
For the remaining resources, we could run a few discovery scans with it.
Application Scanner
We can do the same for Application Scanner
|
|
CPU |
RAM |
|---|---|---|
|
Baseline |
1C |
2GB |
|
Application Assessment x 10 |
6.6C |
22GB |
|
Total |
7.6C |
24GB |
For Application Scanner, we would need more RAM on the VM
|
|
CPU |
RAM |
|---|---|---|
|
Recommended |
8C |
24GB |
|
Consumed |
7.6C |
24GB |
|
Remaining |
0.4C |
0GB |
Bad Dimensioning
From the example above, if your deployment would instead have 12 core CPU and 12 GB of RAM, you would not actually fit more NetSec or Application scans since the scanner would be RAM bound.
Related Articles
- Firewall Rules RC-Scanners
- Install RC-Scanner Appliance
- Deploy RC-Scanner in Hyper-V
- Deploy RC-Scanner on AWS
- Deploy RC-Scanner with KVM/QEMU
- Install RC-Scanner on Hardware
- Deploy/Install RC-Scanner Appliance
- Update RC-Scanner Bootstrap
- RC-Scanner Behind a Web Proxy
- RC-Scanner Dimensioning Guide
- RC-Scanner FAQ
- Deploy RC-Scanner on Microsoft Azure
- Supported Deployment Platforms for RC-Scanners