Improving performance with bulk processing

Improving performance with bulk processing

Description	Best practices for improving reporting performance by using bulk processing.
Version as of	8.1
Application	Pega Platform
Capability/Industry Area	Reporting

Getting started

This document provides instructions on how to avoid processing of large sets of results which uses a lot of system resources causing performance issues. Iterative approach helps to achieve same goal without impacting system resources.

Implementing iterative approach with Report definitions and Obj-Browse improves query performance and reduces memory footprint.

Example

A user wants to update 500 000 eligible cases in a nightly batch job with One time utility. Retrieving that high number of records directly degrades application performance.

Steps

Design Option One:

The following approach works for both activity Obj-Browse method and Report Definitions.

1. Define hasMore parameter and set to true before calling Obj-Browse or Report Definition.
   
2. Start looping by using loop option in activities, and configure precondition for that step.
   
3. Obj-browse or Report Definition should use any unique numeric property that is sorted by the ascending order.
   
4. You can do business logic after this step on the results set. Once business logic is done at the end, set values Param.hasMore based on pxMore from Resultset page and set last processed id.
   
   
   Note: The pxMore is set by Pega to true if there are more records left for your query. That is indication for system to continue the loop. When there are no records left, loop precondition fails, and the step is exited.

Design Option Two:

The following approach works only with Report definition.

1. Set Dynamic pagination values for Report Definitions.
   
2. Call report definition in the loop.
   
3. Set the the HasMore parameter value to false when page count matches with current page.
   

Results

It helps to improve overall application performance and can avoid exceptions and timeout issues with DB queries.

A business solution that automates workflows in your organization. Multiple, unrelated applications can be hosted in the same system. You create an application by running the New Application wizard.

A Pega Platform feature for retrieving, analyzing, and using data from business processes. For example, you can create a report with the number of resolved cases per user, and then use the report to assess user performance. You can also sort and filter data to make your report readable and organized.

An interval of time that is defined in a service-level agreement. It is the suggested resolution time for an item, such as a case or stage.

A Pega Platform method, distinct from a Java method. An operation that can be performed by one step of an activity ( Rule-Obj-Activity rule type), or by a Parse Structured rule ( Rule-Parse-Structured rule type).

(Pega Platform version 7.2.2. and later) A rule for creating advanced reports that show detailed information. Replace the Summary View Rule. A report definition rule provides more advanced options for displaying and managing data than the standard reports that you can create in App Studio.

(Deprecated) A configuration of panels (areas) in a harness that support a composite portal. Existing panel sets continue to function. As a best practice, upgrade panel sets to screen layouts.

(Pega Platform version 7.2.2. and later) A rule for creating advanced reports that show detailed information. Replace the Summary View Rule. A report definition rule provides more advanced options for displaying and managing data than the standard reports that you can create in App Studio.

A reference to a when condition rule (Rule-Obj-When rule type) or an expression that is associated with one step of an activity. After the previous step of an activity runs, before the method in the current step runs, the system evaluates whether the rule or expression is true or false, and performs user-specified behavior based on the result.

The smallest element of your business process, a step represents a single task. A step can be a user action, such as collecting information from a customer, or an automation that an application performs, for example, sending an email to a customer when a business process reaches resolution. When you visualize your work, you order steps in a sequence that communicates what actions are required to reach your business objective. You can select from a wide choice of steps to ensure that you reach your goals in the most efficient way.

A data structure that holds name-value pairs. Pages are stored in the system memory or in the database. Various types of pages are defined in the system, such as data pages that are created when the data is referenced, named and unnamed pages, parameter pages, clipboard pages, and so on. Every unit of information in an application is a pairing of a name and a value, known as a data element. For example, a data element that stores the email address of a customer has the name "email," and the value "john.smith@company.com." Pages store data elements so that the application can use it to process the case.