Optimizing Performance Data Warehouse

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-01-20 10:38
 Traditional: 
 Performance Data Warehouse is not designed to store a large amount of data. You can reduce the number of rows inserted in tables of Performance Data Warehouse by making changes to the property file for Performance Data Warehouse.

About this task

You can make changes to the property file for Performance Data Warehouse to reduce the number of rows in tables.

Procedure

  1. Disable the emission of timing intervals.
    The use of timing intervals in a business process may emit a lot a data and provoke the insertion of a high number of rows in the Performance Data Warehouse tables. If timing intervals are not needed in Performance Data Warehouse, you can disable their emission:
    1. Open each 100Custom.xml file in your topology, as described in Location of 100Custom configuration files.
    2. Edit each 100Custom.xml file and make the indicated edits.
      <performance-server>
   <emit-timing-intervals merge="replace">false</emit-timing-intervals>
</performance-server>
    3. Restart the environment.
  2. Disable the insertion of the Optimizer data.
    The data used by the Optimizer (deprecated) are stored in the Performance Data Warehouse LSW_OPTIMIZER_DATA table that can contain a large number of rows. If the Optimizer is not used in desktop IBM® Process Designer you can disable its insertion:
    1. Open each 100Custom.xml file in your topology, as described in Location of 100Custom configuration files.
    2. Edit each 100Custom.xml file and make the indicated edits.
      <performance-server>
   <insert-optimizer-data merge="replace">false</insert-optimizer-data>
</performance-server>
    3. Restart the environment.
  3. Disable the insertion of tracking data for services.
    By default, services always create Performance Data Warehouse tracking records in the LSW_TASK table when they run. You can disable the insertion of these records:
    1. Open each 100Custom.xml file in your topology, as described in Location of 100Custom configuration files.
    2. Edit each 100Custom.xml file and make the indicated edits in the <server> section:
      <server>
     <service-tracking-enabled merge="replace">false</service-tracking-enabled>
</server>
    3. Restart the environment.