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.
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.
Optimizing response time

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.
- Infrastructure
  The main factor that affects the performance of the BigFix Inventory server is the performance of the underlying infrastructure on which the application server and the DB2 database are running. You must ensure that the recommended requirements are met.
- 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.
- 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.

Optimizing response time

Avoiding calculation of the number of records returned

When executing an API call, use countSwitch=1 attribute to avoid calculating number of reported rows. To return total number of the rows for an API query, use countSwitch=2 and then retrieve pages of the records.

Retrieve total number of available records.

https://hostname:port/api/sam/raw_file_facts?token=token&countSwitch=2

Retrieve first 10000 records by using the limit parameter.

https://hostname:port/api/sam/raw_file_facts?token=token&countSwitch=1&limit=10000&offset=0

Retrieve next 10000 records. You can ignore the already retrieved records by using the offset parameter.
```
https://hostname:port/api/sam/raw_file_facts?token=token&countSwitch=1&limit=10000&offset=10000
```