On the Performance tab, the control of the current document, that is, for example, load balancing, preloading, concurrent session access, and audit logging, can be managed.
Maximum Number of Concurrent Sessions
To choose a maximum number of concurrent sessions towards the current document, enter the desired number in this text box. An empty field means no limit.
Maximum Inactive Session Time
User sessions, which have had no activity during a specified time limit, can be configured to be closed by the QVS. To set the session timeout, enter a suitable figure in this text box.
If left empty or set to 0 means no limit.
Open documents take up valuable system resources (that is, memory space, RAM, is allocated) and should not be allowed to remain open when not in use. However, if a document is closed too quickly, the users may get longer delay times when accessing the document, because the server has to reopen it. This value controls for how long a document will be allowed to be unused before the QlikView Server (QVS) closes the document and reclaims the resources.
To enable the audit log functionality, tick this check box. To disable the audit log functionality, untick this check box.
Select a server in the drop-down list.
If there is more than one server, and if the Customize option was selected in the Document Available field, configure the following:
To configure the load balancing, that is, on which nodes the current document is to be available, select one of the following options:
- Always on All Nodes, meaning availability on all nodes.
- Customize, meaning that the availability can be customized.
If the Customize option was selected in the Document Available field, customize the following:
Presents an auto populated list of all of the servers and clusters, including all cluster nodes, that are selected for distribution.
To configure when the current document is to be available, select one of the following drop-down list options:
- Never, meaning that the current document will never be loaded on the node.
- Always, meaning that the document will always be available to be loaded on the node.