Reduce load on remote artifact servers
A number of properties can be used to reduce the load on remote artifact servers when working with models that include remote artifacts.
- Remote artifacts in Rhapsody models are checked at a regular interval for changes, and if changes are detected, these changes are indicated using an overlay on the Refresh button on the Rhapsody Model Manager toolbar.Actual refreshes of remote artifact information are only carried out when you click the Refresh button or select one of the Refresh options in the model browser menus. The interval for checking for changes is controlled by the RemoteDataChangeDetectionInterval property, whose default value is 900 seconds. The minimum value that can be set for the property is 300 seconds. The RemoteDataChangeDetectionInterval property is located in the Features dialog box. In the Properties tab, change the views to All (default is Common).
The property RemoteDataChangeDetection can be used to control whether or not Rhapsody periodically checks the remote artifact servers to detect if any changes were made to the artifacts included in the currently loaded Rhapsody model.
- If the value of the property is set to Off, these periodic checks are not carried out.
- If the value of the property is set to On, the remote artifact servers are checked for changes according to the interval that was set with the property RemoteDataChangeDetectionInterval.
- When a large number of remote artifacts must be loaded, you can fine-tune performance by modifying the number of threads that are used for the operation. The number of threads that are used is determined by the value of the property RemoteArtifactThreads.
In addition to these properties, there is a property that is called BulkSizeForRetrievingRequirements that can be used for reducing the load on remote requirements servers. The BulkSizeForRetrievingRequirements property controls how many requirements are requested at a time from the requirements server when remote requirements are initially loaded in a model or are refreshed. If you find that requirement loading or refreshing is resulting in too great a load on the requirements server, you can experiment with the value of this property to see whether decreasing or increasing the value improves performance.
The value of this property is also reflected in the behavior of the requirement-loading progress indicator that is displayed next to requirement collections in the model browser. If the value of the property is set to a large number, the progress indicator changes slowly and jumps in large increments. If set to a smaller number, it is easier to see the progress.