Hardware Requirements

Additional hardware resources are required to power the WebUI. Baseline hardware requirements for an BigFix deployment are described in the BigFix Installation Guide.

Capacity planning for the WebUI depends on many factors, including number of endpoints, workload, time of day, server location, and the number of concurrent users. For best practices and recommendations to improve WebUI performance, see the BigFix Capacity Planning Guide, which provides configuration recommendations for the database server, operating system, and hypervisor.

Table 1. Hardware Recommendations for WebUI
Component Additional CPU Additional Memory (GB) Additional Storage (GB)
BigFix WebUI +2 per 10 concurrent users +2 per 10 concurrent users 15% of BigFix database

Starting with BigFix Platform V9.5.5, a database cache is implemented for several counters to improve WebUI response times. The time-based cache has a default refresh interval of 10 minutes.

More about the WebUI Server from the BigFix Capacity Planning Guide:

The BigFix WebUI offers a scalable and highly responsive management interface. There have been a number of iterations of the WebUI server. If you are running an older version an upgrade to the most recent version is strongly recommended. Significant improvements have been delivered providing improved scale, function, and user experience.
  • Hardware recommendations are in addition to BigFix root server requirements.
  • If an anti-collocated instance is deployed (meaning an instance not deployed on the root server), the CPU requirements should be split across the database and WebUI servers, and the storage should be added to the database server.
  • In terms of recommended scalability limits, both the Windows and Linux WebUI instances support 36 concurrent users on a 250k deployment base. Once again, these are highly active concurrent users per the previously provided capacity planning definitions.
  • Concurrent users would typically be non-master operators, managing a subset of the estate.
  • It is possible to manage at a larger scale based on user operations, infrastructure capability, etc. However, the stated bounds should be considered a good rule of thumb for the scale of the solution.