Software-based CLEAR Engine can be installed on a physical server or a virtual machine. The recommended system specification differs between the instance scale, the applications it will scan, and the frequency of the scans. This guide provides a guidance on choosing the right system configuration for CLEAR Engine.
This article covers the hardware aspects of the system. To learn more about other system requirements or recommendations, such as operating system, view the following article in the Lucent Sky Knowledge Base:
Administration guide to CLEAR Engine and Web UI
In this article, you will learn how to:
- Determine the instance scale
- Choose the right system configuration for CLEAR Engine
At the end, you will be able to determine the instance scale, and choose the right system configuration for CLEAR Engine.
Determine the instance scale
There are three primary sectors determining the scale of the instance:
- The number of applications it will scan in the same time
- This is also called "concurrent scans"
- Consider peak periods when a larger number of applications might need to be scanned at a short period of time
- The size of the largest applications it will scan:
- XS - below 500 thousand lines of code and below 100 MB of library
- Small - between 500 thousand to 1 million lines of code and below 100 MB of library
- Medium - between 1 to 2 million lines of code and between 100 to 200 MB of library
- Large - between 2 to 4 million lines of code or above 200 MB of library
- XL - above 4 millions lines of code
- The desired scan performance:
- Balanced - balances scan performance with computing cost
- High performance - favors scan performance over computing cost
Choose the right system configuration for CLEAR Engine
Basic principals
- The installed processor cores should be double of maximum concurrent scans. For example, a system with 4 maximum concurrent scans should have 8 processor cores.
- The installed memory (in GB) should be 4 times (for small applications), 8 times (for large applications), or 16 times (for XL applications) of maximum concurrent scans. For example, a system expected to scan 4 large applications concurrently should have 32 GB of memory for large applications.
- The available disk space should be quadruple of the size of scans that will persist on the system. For example, if 10 applications, each is 100 MB of size, are scanned daily, and historical scan will persist 30 days, the system should have at least 120 GB of disk space available to CLEAR Engine.
Reference system specifications
A1
1-core Standard Edition, mostly small applications, balanced configuration
- Processor: two 2.4 GHz processors
- Memory: 8 GB
- Storage: 100 GB, 4,000 IOPS
A2
2-core Standard Edition, mostly small applications, balanced configuration
- Processor: four 2.4 GHz processors
- Memory: 8 GB
- Storage: 200 GB, 4,000 IOPS
D2
2-core Standard Edition, mostly small applications, high performance configuration
- Processor: four 3.6 GHz processors
- Memory: 8 GB
- Storage: 200 GB, 8,000 IOPS
D4
4-core Standard Edition, mostly small applications, high performance configuration
- Processor: eight 3.6 GHz processors
- Memory: 16 GB
- Storage: 400 GB, 8,000 IOPS
F1
1-core Enterprise Edition, mostly medium applications, balanced configuration
- Processor: two 3.0 GHz processors
- Memory: 8 GB
- Storage: 100 GB, 4,000 IOPS
F2
2-core Enterprise Edition, mostly medium applications, balanced configuration
- Processor: four 3.0 GHz processors
- Memory: 16 GB
- Storage: 200 GB, 8,000 IOPS
F4
4-core Enterprise Edition, mostly large applications, balanced configuration
- Processor: eight 3.0 GHz processors
- Memory: 32 GB
- Storage: 200 GB, 8,000 IOPS
H2
2-core Enterprise Edition, mostly medium applications, high performance configuration
- Processor: four 3.6 GHz processors
- Memory: 16 GB
- Storage: 200 GB, 8,000 IOPS
H4
4-core Enterprise Edition, mostly large applications, high performance configuration
- Processor: eight 3.6 GHz processors
- Memory: 64 GB
- Storage: 400 GB, 16,000 IOPS