Large environment guidelines

For environments containing up to 250K targets, you can use server installation type 3 described in Server environment guidelines.
Note: 250K targets include a maximum number of 60K targets running in Unattended mode.
Also, consider the following extra requirements:
  • End-to-end network latency below 50 ms across the whole environment (Server, Database, Broker, Targets).
  • Log Level = ERROR on the Server. Higher log verbosity significantly increases I/O and reduces the supported total.
  • Heartbeat configuration as defined in the Heartbeat configuration table, including rc.unattended.heartbeat.interval.minutes = 2 and heartbeat.timeout = 1440.
  • The Server runs on real physical hardware matching the specifications listed below. Performance can degrade on virtualized servers; an additional sizing margin is recommended in that case.
To host Open Liberty Application Server
  • Processors: 2 Quad core processors. 2.40 GHz with supported OS.
  • Memory: 16 GB RAM.
  • Storage: Very fast SSD disks.
  • Heartbeat configuration: See the table below.
    Table 1. Heartbeat configuration properties: suggested values for a large environment
    Property in trc.properties Value
    heartbeat.timeout1 1440
    heartbeat.retry 60
    heartbeat.delay 60
    heartbeat.on.wake 0
    heartbeat.on.user.change 1
    heartbeat.on.change 0
    heartbeat.on.stop 0
    rc.unattended.heartbeat.interval.minutes2 2
  1. Note: If there are specific groups of computers where more regular updates are needed, a smaller heartbeat timeout setting can be applied as a group attribute for those specific groups of targets. For details of setting this attribute at group level, see the chapter that explains how to create a target group in the BigFix® Remote Control Administrator's Guide.
  2. Note: Heartbeat interval, in minutes, used by Unattended-mode targets. Defined in the Unattended Target section of trc.properties. This value is part of the scalability baseline: lowering it increases Server overhead and reduces the supported total.
To host the database
  • Processors: 4 Quad core processors, 2.40 GHz.
  • Memory: As recommended by the database supplier.
  • Storage: Very fast SSD disks (146 GB).
Note: The database administrator must tune the database for appropriate performance.

Additional guidelines for large reports

The following guidelines must also be considered when you use large reports, as some performance degradation can be experienced.
  • Ensure that the All targets report is not the default home page report.
  • Ensure staged deployment of the targets to avoid overload in the server when they try to register.
    Note: Give the RegistrationDelay target property a value that distributes the target computer registration evenly through the staged deployment. Distribute the target registration to avoid too many computers trying to register at the one time.
Note for LDAP: If you configure LDAP and LDAP synchronization is enabled, set a reasonable frequency for the synchronization. If your LDAP configuration is set up to import many users and groups, set the frequency to 24 hours. For more information about configuring LDAP, see Configure LDAP.
Note for Microsoft Entra ID: If you configure Microsoft Entra ID and Microsoft Entra ID synchronization is enabled, set a reasonable frequency for the synchronization. If your Microsoft Entra ID configuration is set up to import many users and groups, set the frequency to 24 hours. For more information, see Configure Microsoft Entra ID.