Performance optimizations are made available for saving work items that contain a large amount of related objects (such as Configuration Items or Reviewers) by using the PrePopulateCiLimit setting. This optimization involves querying SCSM for all related objects before performing the save, rather than querying for them one by one throughout the save routine. However, it has been discovered in environments where there are an extremely large amount of Configuration Item Classes this optimization causes a save delay due to the size of the query statement that is created by the Microsoft SDK. Â
To accommodate this scenario, the setting item called PrePopulateCiLimit can be used. The value of this setting is an integer with a default of 1. Meaning any work item that has at least 1 related Configuration Item will perform the query to prepopulate before the save occurs. For environments with large amounts of CI classes this number can be increased to something more appropriate such as 10, in this case the prepopulate would only occur if the work item being saved had more than 10 related CIs. This setting can be configured using the Admin Settings Item page.
Important note: Increasing the value of the PrePopulateCiLimit will cause a performance impact exponentially as the amount of related CIs increases. This setting is meant to be used at the client's discretion in order to find a happy medium for their environment.