6 Tuning Rerating Performance

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

Topics in this document:

• Improving pin_rerate Performance

• Setting the Rerating Event Cache Size (Fetch Size)

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

See also:

• About Rerating Events

• Configuring BRM to Create Rerate Jobs Automatically

• Processing Events in Rerate Jobs

• Configuring BRM to Rerate Events

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 event_fetch_size in the Connection Manager's configuration file 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. Open the Connection Manager (CM) configuration file (BRM_home/sys/cm/pin.conf) using a text editor.

2. Uncomment the - fm_subscription event_fetch_size entry.

3. Edit the event_fetch_size value. The default is 10000.

   - fm_subscription event_fetch_size 10000
   

4. Save the file.

5. Stop and restart the CM.

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.