Set partition size for parallel loading-enabled Azure accounts
Optimize the performance of data sources by setting the partition size in the azure_full_pull_partition_size system property.
Before you begin
Set the application scope to Service Graph Connector for Microsoft Azure using the application picker. For more information, see Application picker.
Role required: admin
About this task
The parallel loading feature is available for the following data sources:
- Starting with the Service Graph Connector for Microsoft Azure 1.13.0 version:
- SG-Azure Functions
- SG-Azure Generic Resources
- SG-Azure Get Run Command
- SG-Azure Hardware Template Updation​
- SG-Azure HW Consolidation​
- SG-Azure Kubernetes Cluster
- SG-Azure Load Balancers
- SG-Azure Network Interface
- SG-Azure Public IP Address
- SG-Azure Run Command
- SG-Azure Scale Sets VMs
- Starting with the Service Graph Connector for Microsoft Azure 1.11.0 version:
- SG-Azure Network
- SG-Azure Virtual Machines
- SG-Azure Storage Volume
For a full data pull, the azure_full_pull_partition_size property determines the number of Azure subscriptions that can be executed as parallel jobs to retrieve configuration item (CI) data. Partition size determines how many Azure subscriptions a single parallel-thread evaluates for data retrieval. If you set the azure_full_pull_partition_size property to 100, the partition size is 100
subscriptions.
Note:
If the azure_full_pull_partition_size property isn't configured, the partition size computation feature of the Integration Commons for CMDB application automatically determines the partition size for parallel loading at runtime. See Partition size computation for parallel loading in Integration Commons for CMDB.