Posted: 29 Jan 2019 17:36 EST Last activity: 19 Feb 2019 21:00 EST
What does Limit to a single data page checkbox does?
For thread scope data page, there is a check box under Load Management tab called Limit to a single data page. Strangely enough, help doesn't describe the effect of ticking that box. Does anyone know what is the effect? Does it mean that only a single instance of the data page is kept on the clipboard regardless of the parameters? What will be a scenario for this checkbox to be useful?
For read-only data pages with a scope of Requestor or Node, select the Clear pages after non-use check box to force the system to delete the clipboard instances of the data page after an interval passes with no access. Subsequent attempts by a requestor to access the data pages cause the pages to reload. This setting does not apply to editable data pages.
When selected, this setting has different effects depending on the scope of the data page:
Requestor scope – The data page instance that is created when any thread refers to the data page is removed when there are no more threads referring to it.
Node scope – The system checks the Reload if older than fields on the Load Management tab of the data page rule. If the fields are blank, the system uses the value of the Dynamic System Setting DeclarePages/DefaultIdleTimeSeconds, which is set by default to 86400 seconds, or one day.
Note: Read-only data pages are never passivated. If a requestor or thread is idle and gets passivated, all read-only data pages in that requestor or thread are cleared and reloaded the next time they are referenced, whether or not Clear pages after non-use is selected.
Thanks for the reply. It confirms what I suspect is the effect of the checkbox, but it doesn't really explain the underlying intended benefit of using it. I suppose it is only to reduce the number of data pages in memory when it is expected that the data page will be called with a very high number of different parameters.