6 Tuning Rerating Performance

Learn how to improve performance for Oracle Communications Billing and Revenue Management (BRM) rerating.

Topics in this document:

See also:

Improving pin_rerate Performance

The following pin_rerate configuration parameters can be used with pin_rerate -rerate option to improve pin_rerate performance: 

- pin_rerate  rerate_children  5 
- pin_rerate  rerate_per_step  1000 
- pin_rerate  rerate_fetch_size  5000

Note:

These entries can only be used with pin_rerate -rerate option.

Setting the Rerating Event Cache Size (Fetch Size)

By default, BRM rerating caches 10,000 events in system memory for processing. Depending on your system memory, you can set the EventFetchSize business parameter to specify the number of events retrieved from the database and cached in the system memory for processing.

To set the event cache size:

  1. Go to BRM_home/sys/data/config.
  2. Use the following command to create an editable XML file from the subscription instance of the /config/business_params object:
    pin_bus_params -r BusParamsSubscription bus_params_subscription.xml

    This command creates an XML file named bus_params_subscription.xml.out in your current directory. If you do not want this file in your current directory, specify the path as part of the file name.

  3. In bus_params_subscription.xml.out, set EventFetchSize to the required cache size: 
    <EventFetchSize>value</EventFetchSize>

    The default value is 10000.

    Caution:

    BRM uses the XML in this file to overwrite the existing instance of the /config/business_params object. If you delete or modify any other parameters in the file, these changes affect the associated aspects of the BRM configuration.
  4. Save and exit the file.
  5. Rename the bus_params_subscription.xml.out file to bus_params_subscription.xml.
  6. Use the following command to load your changes into the /config/business_params object:
    pin_bus_params bus_params_subscription.xml

    You should run this command from the BRM_home/sys/data/config directory, which includes support files used by the utility. To run it from a different directory, see "pin_bus_params" in BRM Developer's Guide.

  7. Read the object with the testnap utility or the Object Browser to verify that all fields are correct.

    For general instructions on using testnap, see "Using the testnap Utility to Test BRM" in BRM Developer's Guide. For information on how to use Object Browser, see "Reading Objects" in BRM Developer's Guide.

  8. Stop and restart the CM.

    For more information, see "Starting and Stopping the BRM System" in BRM System Administrator's Guide.

Configuring the Number of Accounts Per Job and Number of Jobs per Transaction

To prepare for rerating, BRM assigns accounts to rerate jobs. By default, BRM assigns 10 accounts to each rerate job and creates 2 rerate jobs per transaction. For performance tuning, you can change the default number of accounts per job and the number of rerate jobs created per transaction:

  1. Open the pin_rerate configuration file (BRM_home/apps/pin_rerate/pin.conf).

  2. Set the number of accounts assigned to each rerate job by adding the following line:

    - pin_rerate per_job accounts_per_job

    where accounts_per_job is the number of accounts to assign to each job.

  3. Set the number of jobs created per transaction by adding the following line:

    - pin_rerate per_transaction jobs_per_transaction

    where jobs_per_transaction is the number of jobs to create in each transaction.

  4. Save and close the file.

    Note:

    Setting the pin_rerate per_job entry to a small number, for example 1, results in many rerate jobs being created. Too many rerate jobs can affect your system's performance due to the rerate steps performed for each rerate job. Processing multiple accounts in one rerate job reduces the total number of rerate steps performed compared to processing those same accounts in multiple rerate jobs.