Challenge
Assessing application performance
Assessing application performance
2 Tasks
10 mins
Intermediate
Low-Code App Development
Performance
English
Scenario
The Human Resources (HR) department has noticed that the open positions screen of the candidate Case Type has been loading the list of positions slowly for some users. Investigate the performance characteristics of the screen and implement improvements that will reduce the loading time of the positions.
The following table provides the credentials you need to complete the challenge.
| Role | User name | Password |
|---|---|---|
| Senior System Architect | SSA@TGB | pega123! |
Note: This challenge does not have a demo video. Please refer to the Detailed Tasks for step-by-step instructions to complete the challenge.
Detailed Tasks
1 Establish the initial baseline performance with PAL
- In the Pega instance for the challenge, enter the following credentials:
- In the User name field, enter SSA@TGB.
- In the Password field, enter pega123!.
- In Dev Studio, launch the Web portal and create a new Candidate case.
Tip: Creating a new case prevents the first load from skewing performance results.
- In the header of the Web portal,click the Account > PAL Profiler to launch PAL Profiler.
- In the PAL Profiler window, click the Reset to set the counts to zero.
- Click Add reading to add a row of summary performance data.
- In the Web portal, create another new Candidate case.
- In the PAL Profiler window, click Add reading to add another row of summary performance data.
- Take a screenshot or make a note of the Total Elapsed and Total CPU numbers on the first DELTA line, as shown in the following image. These values are the baseline performance of the Collect Personal Details screen.
Note: The Total Elapsed and Total CPU values may vary from the image. Take a screen capture of the PAL Profiler window as a way to document the performance values.
2 Enhance runtime performance
- In Dev Studio, click Data types > Position > List Position to open and edit the List Position Data Page.
- In the Data page definition section, in the Scope list, select Requestor to prevent 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, in the Refresh strategy section, verify that the Reload once per interaction check box is cleared to ensure the Data Page stays in memory and is only refreshed if the information is older than one hour, the default reload time.
- Save and close the Data Page rule.
Note: If the Data Page is in a locked Ruleset, save a copy of the Data Page into the highest available unlocked Ruleset.
- Log off from the instance.
This Challenge is to practice what you learned in the following Modules:
Available in the following mission:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?