Assessing application performance
1 Task
10 mins
Intermediate
Low-Code App Development
Performance
English
Scenario
You are a Solution Builder at TGB. The HR department reports that the open positions screen of the Candidate Case Type loads slowly. Your goal is to investigate the performance of the application and implement improvements.
You use the PAL Profiler to capture a baseline performance reading, adjust the scope of the List Position Data Page to reduce memory use and processing time, and confirm the Load Management settings on the Data Page.
Note: This challenge has been configured with Single Sign-On (SSO) using your Pega Academy credentials. If you are not automatically signed in to the challenge environment after initializing the instance, you may use the credentials provided.
The following table provides the credentials you need to complete the challenge:
| Role | User name | Password |
|---|---|---|
| Solution Builder | SSA@TGB | pega123! |
After completing this challenge, you should be able to:
- Use the
PAL Profilerto capture a baseline performance reading. - Improve Data Page performance by setting the appropriate scope.
- Configure Load Management settings on a Data Page.
Detailed Tasks
1 Assessing application performance
Use the technical documentation linked in the Journey map above to complete the assigned tasks. The technical documentation might have more information than you need to complete the tasks.
Acceptance criteria
Task 1: Establish baseline performance with the PAL Profiler
- The
PAL Profileris reset and an initial reading is added before creating a new Candidate case. - After creating a new Candidate case, a second reading is added.
- The
Total ElapsedandTotal CPUvalues from the firstDELTAline are recorded as the baseline for the new Candidate case creation.
Task 2: Enhance runtime performance of the List Position Data Page
- The D_PositionList Data Page is updated with the following configuration in the Data page definition section:
Field Value Scope Requestor - Setting the Scope to Requestor prevents the Data Page from being created for every new Thread instance in the application, saving on memory space and processing time.
- On the Load Management tab, the following setting is confirmed:
Field Value Reload once per interaction Unchecked - Clearing this checkbox ensures the Data Page stays in memory and is only refreshed if the information is older than one hour, the default reload time.
Directions
- Launch the Web portal and create a new Candidate case.
- Open the
PAL Profilerfrom Account settings. - Reset the profiler and add a reading.
- Create another new Candidate case and add a second reading.
- Record the
Total ElapsedandTotal CPUvalues from the firstDELTAline as the baseline. - Save your changes.
- Open the List Position Data Page in the Position Data Type and update it as detailed in the Acceptance criteria.
- Save your changes.
This Challenge is to practice what you learned in the following Module:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?