Implementation Guide › Implementation › Business Logic Scripting (Business Logic Expert) › Inside the Business Logic › Optimize the System for Recalculation

Optimize the System for Recalculation

The service level calculation process requires significant amount of CPU resources, memory and storage. Following is a list of recommendations that can reduce machine load and improve calculation speed.

Note: Some of these recommendations require internal settings not available in the user interface. In such cases, contact CA technical support for more details and instructions.

• Change the states saving configuration

  Depending on the Adapter's known delays, you can set the states parameters to better suit your requirements; meaning you can change the number and granularity of the states' save points.

• Configure the system to calculate only the time units that are really needed

  Metrics can have up to seven different granularities periods: year, quarter, month, week, day, hour, and tracking period. In some implementations, not all the granularities are necessary. You can turn off unnecessary granularities for uncommitted contracts, via the user interface. Refer to each Metrics granularities tab. For changing a committed contracts Metric granularities, contact CA technical support.

  Note: Avoid calculation of operational periods that are similar to the tracking period.

• Do not calculate "without correction", "without exceptions" values

  By default, the calculation engine calculates four different values: provided, provided with corrections, provided with exceptions, and provided with corrections and exceptions. You can change this to calculate only the provided value.

  Note: For more information, contact CA technical support.

• Change the calculation order

  The PSL calculation order of Metrics can be prioritized to start with your more important Metrics and then to continue to the other Metrics.

  Note: For more information, contact CA technical support.

• Create more then one PslWriter instance

  By creating more than one PSL instance (of the calculation engine), you can split the workload and increase the calculation speed.

  Note: For more information, contact CA technical support.

• Plan implementations to shorten recalculation time

  To optimize recalculation time, you can:

  • Run the Adapter more often in order to reduce delayed events and avoid large backlogs of data for the Engine to process
  • Turn off unused agents in the Metrics granularity tab.
  • Duplicate Metrics and calculate different agents using the same Metric, to balance the calculation load
  • Use intermediate Metrics to perform common calculations and share the results with all the other Metrics who require the same data.
• Plan implementations to reduce the amount of data

  To optimize the amount of data, use the Adapter to load only aggregated (processed) data. Aggregating the data source information before it is sent to CA Business Service Insight Raw Data Table increases the PSL input reading efficiency.

• Follow CA Business Service Insight PSL configurations recommendations

  The PSL Engine can be reconfigured for better performance according to the specific application environment and requirements. Some of the parameters can be set from the user interface and others can be set only from the database system configuration table.

  Note: Consult support recommendations for your PSL configurations.