Sizing
Note: Forcepoint Data Classification and Forcepoint DSPM require minimum server specifications for installation; they will not deploy on undersized
servers.
Server sizing indicates the utilization of resources used by the Forcepoint DSPM solution based on customer workload. Any sizing provided can be subject to change due to environmental variables.
We outline below some of the variables that can affect the sizing:
- Server resources: These include physical vs virtual, physical underlying CPU, RAM, and disc specs/speeds and whether they are shared or dedicated.
- Network (speed, latency, and throughput)
- Geolocation
- Specific location of the server (data center or Azure, AWS, GCP, etc.)
- Amount of data
- Distribution of file types and sizes across the scanned data set (type, size, number of files, etc.)
- Vendor throttling
Note: Sizing may require adjusting once the platform is operational to meet data classification scanning speed requirements/expectations. Please note that scaling is not linear - you do not need
to double the size of the server to double the speed. To double the classification throughput, you may only need to add an additional 2 CPUs and 6GB RAM.
If data/users are spread across multiple geolocations, a server per location is needed, and then you need to size each server accordingly.