Depending on the size of the infrastructure to be discovered, the vScope server needs to be configured with the right hardware settings to run smoothly. Here is a list of suggested configurations of the vScope server.
2-4 CPU cores recommended
In most scenarios two cores will be more than enough.
Depending on the size of the infrastructure to be discovered, the recommended size of the HDD can vary from 60 GB up to 200 GB. Please consult with an InfraSight rep with more exact recommendation.
To benefit from the best possible vScope experience, SSD or similar storage with high IOPS rating recommended
Throughput is important but not as important as IOPS (I/O Operations Per Second)
The vScope database contains historical data which means that data will be spread across the storage medium with time resulting in mostly what is called random reads.
One random read translates into one I/O operation. SSDs usually have a much higher IOPS rating than mechanical disks: 10000+ vs 100-200.
Recommended is to allocate 8+ GB RAM to the vScope server. The benefit of having plenty of RAM on the server running vScope is that frequently accessed data can be kept “hot” in RAM before having to read it from disk.
It is recommended that vScope is assigned 2/3 of the RAM available on the server with a minimum of 4 GB left to the OS to allow the OS to use the remaining RAM for the OS disk cache. The OS disk cache will help vScope in keeping frequently accessed data in RAM.
Server: 8 GB, vScope 4 GB
Server: 12 GB, vScope 8 GB
Server: 16 GB, vScope 10 GB
Server: 24 GB, vScope 16 GB
Server: 32 GB, vScope 20 GB
Server: 48 GB, vScope 24 GB