360 GRC's ConfigScan Minimum System Requirements
| Number of Devices |
VMware Hypervisor (*) |
Standalone Physical Server |
Core Processors (**) |
Memory (***) |
Storage Space (****) |
Database location |
Screen Resolution |
| 50 |
ESX 4.0 |
Not necessary |
Dual core 2.4GHz + |
4Gbps |
100Gbps 7500rpm |
Same server |
1024x768 or better |
| 100 |
ESX 4.0 |
Not necessary |
Dual core 2.4GHz + |
4Gbps |
150Gbps 7500rpm |
Same server |
1024x768 or better |
| 200 |
ESX 4.0 |
Not necessary |
Quad core 2.4GHz + |
8Gbps |
250Gbps 10,000rpm |
Same server |
1024x768 or better |
| 400 |
ESX 4.0 |
Not necessary |
Quad core 2.4GHz + |
8Gbps |
400Gbps 10,000rpm |
Separate VM or physical Server |
1024x768 or better |
| 600 |
ESX 4.0 |
Not necessary |
Quad core 2.4GHz + |
8Gbps |
600Gbps 10,000rpm |
Separate VM or physical Server |
1024x768 or better |
| 1000 |
ESX 4.0 |
Recommended |
Quad core 2.4GHz + |
8Gbps |
700Gbps Storage center |
Separate VM or physical Server |
1024x768 or better |
| 2000 |
Not recommended |
Recommended |
Quad core 2.4GHz + |
8Gbps |
1 Terabyte Storage center
|
Separate VM or physical Server |
1024x768 or better |
| 3000 |
Not recommended |
Recommended |
Quad core 2.4GHz + |
8Gbps |
1 Terabyte Storage center |
Separate VM or physical Server |
1024x768 or better |
| 5000 |
Not recommended |
Recommended |
Quad core 2.4GHz + |
8Gbps |
1 Terabyte Storage center |
Separate VM or physical Server |
1024x768 or better |
| 7000 |
Not recommended |
Recommended |
Quad core 2.4GHz + |
8Gbps |
1 Terabyte Storage center |
Separate VM or physical Server |
1024x768 or better |
| 8000 |
Not recommended |
Recommended |
Quad core 2.4GHz + |
8Gbps |
1 Terabyte Storage center |
Separate VM or physical Server |
1024x768 or better |
| 10000+ |
Not recommended |
Recommended |
Quad core 2.4GHz + |
8Gbps |
1Terabyte Storage center |
Separate VM or physical Server |
1024x768 or better |
(*)It is strongly recommended that VMware ESX server is used. VMware HyperVisor choices in order of preference are: ESX 4.0 (most preferred), ESX 3.5 (least preferred).
(**)Performance can and will be impaired with other applications running on the same VM server as ConfigScan, especially if the number of processor cores assigned to ConfigScan is less than half of the total processor cores on the VM ESX server.
(***) Performance will be impaired if the right amount of memory is not used, especially when reports are being generated. It is recommended to use as much memory as possibly available as is a critical factor to overall performance.
(****)Disk performance is another critical factor for overall performance. The more spindles dedicated to ConfigScan, the better. It is recommended for larger enterprise customers to use specialized RAID configurations, with average seek times for 4msec or better and using LUNs for dedicated storage farm could be used also for large disk storage.
