Question
HCL
IN
Last activity: 27 Feb 2020 15:17 EST
Data Page size limit
Hi Team,
Can anyone please let me know the below queries:
1. How much of results can a list data page hold?
2. How much of data page instances be available in memory at node level?
Thanks
Vignesh.
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
FR
Hello,
I don't think we have any hard coded size. I guess it depends on your jvm, what size are you expecting exactly?
Updated: 14 Jun 2021 7:38 EDT
Pegasystems Inc.
IN
I don't think there is a limit for results in Datapage. However if we want we can limit in Data Page sources like Report definition
Pegasystems Inc.
US
Hi, did some quick research and found below, hope this would help you!
The number of data page instances for a container reaches the set limit
By default, the Pega 7 Platform can maintain 1000 read-only unique instances of a data page per thread. You can change this value by editing the dynamic system setting datapages/mrucapacity.
There are different data page instance containers for the thread, requestor, and node level. Each user can have both requestor-level and thread-level data pages up to the limit established. Additionally, each node can have any number of requestors, and each requestor can have many threads. See Contrasting PRThread objects and Java threads.
For each container:
Hi, did some quick research and found below, hope this would help you!
The number of data page instances for a container reaches the set limit
By default, the Pega 7 Platform can maintain 1000 read-only unique instances of a data page per thread. You can change this value by editing the dynamic system setting datapages/mrucapacity.
There are different data page instance containers for the thread, requestor, and node level. Each user can have both requestor-level and thread-level data pages up to the limit established. Additionally, each node can have any number of requestors, and each requestor can have many threads. See Contrasting PRThread objects and Java threads.
For each container:
- If the number of instances of a data page reaches 60% of the established limit for thread-level or requestor-level containers, or 80% of the established limit for node-level containers, the system begins deleting older instances.
- If the number reaches the established limit, the system deletes all data page instances that were last accessed more than 10 minutes ago for that container.
- If, after that step, the number of instances of the data page still exceeds the set limit, the system tolerates an overload up to 125% of the established limit for thread-level or requestor-level containers, or 120% of the established limit for node-level containers.
- If the number exceeds that overload number, the system deletes instances (regardless of when they were last accessed) until the number of entries in the cache is below the set limit.
Pegasystems Inc.
US
You may find more information at this link
https://community.pega.com/knowledgebase/articles/pega-7-management-data-pages#set-limit
Pegasystems Inc.
US
The default value for DATA-ADMIN-SYSTEM-SETTINGS PEGA-RULES!DATAPAGES/MRUCAPACITY learnt from Pega 7.1.9 is 1000.
Pegasystems Inc.
IN
1. How much of the results can a list data page hold?
There is no limit. however, it depends on the JVM memory
2. How much of data page instances be available in memory at node level?
By default, the Pega 7 Platform can maintain 1000 read-only unique instances of a data page per thread
which can be changed on the DSS DATAPAGES/MRUCAPACITY