Master Profile cache
The 8.2 version of the application introduces some changes how the master profile is
loaded and saved so that the overall performance of the application improves. No changes are
required to use the new mechanism unless some kind of customization has been done in that
part of the application. A proper impact assessment is required in that case. The new model keeps the interface with the rest of the application unaltered.
Customers are still expected to retrieve the Master Profile using
GetMasterProfile (data retrieval plus synchronization) and
D_GetMasterProfile (data retrieval). The persistence of the
data is still expected through SaveWorkFolder. The main changes are implemented when loading
D_GetMasterProfile, a thread level data page loaded in every
interaction. The changes ensure that the master profile is only loaded from the
database when data has changed. Otherwise, it reuses information already in
memory. The following two data pages support this new mechanism: To make the most of this mechanism and to automatically adopt it in future related
features, it is important that customers let the application manage the master
profile or, if required, access it using the existing interface as defined above
(GetMasterProfile/SaveWorkFolder). To enable customers to find the right balance between memory footprint and
performance in their applications, the Master Profile access mechanism support two
different working modes: To keep the growth of the cache under control, the application maintains a limit in
the number of Master Profiles that can be maintained in the cache. By default, the
application is configured to manage no more than ten Master Profiles, but this is a
threshold that can be changed through configuration. clmfs/MasterProfileCache/Enabled clmfs/MasterProfileCache/SizeAccessing the Master Profile
Configuring the Master Profile cache
Dynamic system settings Value PegaCLMFS Flag to activate the access to the Master Profile through
cache. When the value is set to true, the
system makes use of the cache. A value of
false bypasses the cache. PegaCLMFS
Number of active instances in the Master Profile for the
requestor. When no value is set, the system uses a value of
10.
Previous topic Configuring asynchronous processing Next topic Know Your Customer Engine