Home
Tuning performance
Learn how to plan the infrastructure of BigFix Inventory and to configure the application server to achieve optimal performance. The following guidelines are applicable in big data environments as well as in smaller environments that are running on low-performance hardware.
Tuning performance in medium and large environments
You can learn the possible causes of the most common performance issues in medium and large environments. Follow the tips and the known solutions to these issues to keep the system in good shape and avoid performance problems.
Tuning DB2 application database
To avoid performance issues in medium and large environments, configure the location of the transaction log and adjust the log size. If you are using DB2 as BigFix Inventory database, you might want also to change the swappiness parameter in Linux or configure the DB2_COMPATIBILITY_VECTOR.
Configuring the transaction log location for DB2
To increase database performance, move the DB2® transaction log to a file system that is separate from the DB2 file system.

Tuning performance
Learn how to plan the infrastructure of BigFix Inventory and to configure the application server to achieve optimal performance. The following guidelines are applicable in big data environments as well as in smaller environments that are running on low-performance hardware.
- Setting up scans and import
  Learn how to improve the scanning and importing activities to optimize the performance in your infrastructure.
- Additional tasks for improving performance
  Learn about additional tasks that you might want to perform to improve the performance in your infrastructure.
- Tuning performance in medium and large environments
  You can learn the possible causes of the most common performance issues in medium and large environments. Follow the tips and the known solutions to these issues to keep the system in good shape and avoid performance problems.
  - Tuning DB2 application database
    To avoid performance issues in medium and large environments, configure the location of the transaction log and adjust the log size. If you are using DB2 as BigFix Inventory database, you might want also to change the swappiness parameter in Linux or configure the DB2_COMPATIBILITY_VECTOR.
    - Maintaining the DB2 database
      To ensure that the DB® database works properly, you need to regularly back up your data and perform maintenance actions.
    - Configuring the transaction logs size
      If your environment consists of many endpoints, increase the transaction logs size to improve performance.
    - Configuring the transaction log location for DB2
      To increase database performance, move the DB2® transaction log to a file system that is separate from the DB2 file system.
    - Configuring swappiness in Linux hosting DB2 database server
      Swappiness determines how quickly processes are moved from RAM to hard disk to free memory. It can assume the value 0 - 100. A low value means that your Linux™ system swaps out processes rarely while a high value means that processes are written to disk immediately. Swapping out runtime processes should be avoided on the DB2® server on Linux, so it is advisable to set the swappiness kernel parameter to a low value or zero.
    - Configuring the DB2_COMPATIBILITY_VECTOR variable for improved UI performance
      For environments with 5000 or more clients in your infrastructure, set the value of the DB2_COMPATIBILITY_VECTOR variable to MYS. The change in the value might result in faster UI response time on some installations. For information about how to modify the registry variable, refer to DB2_COMPATIBILITY_VECTOR registry variable.
    - Configuring statement heap size
      Statement heap size configuration parameter (stmtheap) refers to the limit of the statement heap, which is used as a workspace for the SQL compiler during compilation of an SQL statement. Statement heap size has an impact on the time taken to execute complex queries, for example generating the audit snapshot.
  - Tuning MS SQL application database
    To avoid performance issues in medium and large environments, configure the location of the transaction log. If you are using MS SQL as BigFix Inventory database, you might want to shrink the transaction log or update query optimization statistics.
- REST API considerations
  You can use BigFix Inventory REST API to retrieve large amounts of data that is related to computer systems, software instances, and license usage in your environment. Such information can then be passed to other applications for further processing and analysis.

Configuring the transaction log location for DB2

To increase database performance, move the DB2® transaction log to a file system that is separate from the DB2® file system.

About this task


Medium environments:	Strongly advised
Large environments:	Required
Very large environments	Required

Procedure

To move the DB2® transaction log to a file system that is separate from the DB2® file system, update the DB2® NEWLOGPATH parameter for your BigFix Inventory database:
```
UPDATE DATABASE CONFIGURATION FOR TEMADB USING NEWLOGPATH value
```
Where value is a directory on a separate disk (different from the disk where the DB2® database is installed) where you want to keep the transaction logs. This configuration is strongly advised.
For the changes to take effect, restart the database. Run the following commands:
```
DEACTIVATE DB TEMADB
DB2STOP
DB2START
ACTIVATE DB TEMADB
```
Restart the BigFix Inventory server.
1. To stop the server, run the following command:
```
/etc/init.d/BFIserver stop
```
2. To start the server, run the following command:
```
/etc/init.d/BFIserver start
```