Which approach solves this performance issue?

Your application is deployed to the cloud. A data source outside your application populates a data page by using your data access pattern configuration. You receive complaints that the system takes a long time to fetch data each time the case worker accesses information for a different customer.

Which approach solves this performance issue?
A . Access data page with a predefined key so that, once loaded, data access is faster.
B . Fetch only the targeted data from the database each time data is needed so access is faster.
C . Change snapshot data access method to reference pattern data access method.
D . Move to local installation because network traffic in cloud deployment is often slow.

Answer: A

Explanation:

Using a data page with a predefined key enhances performance by leveraging the caching mechanism of Pega. When a data page is loaded with a specific key, it is stored in memory. Subsequent accesses to the data page with the same key do not require fetching the data again from the external data source, significantly reducing the access time. This approach is particularly beneficial in cloud deployments where network latency can impact performance. It ensures that once the data for a particular customer is fetched and stored in the cache, accessing the same customer’s information again is much faster, addressing the performance issue reported.

Reference: Pega Community documentation on data pages and performance best practices.

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments