|
|
When a user opens a dashboard, changes filter options or selects a drill down in the web or mobile apps, that request must be processed by the web server. If the dashboards contain a lot of data and the number of requests are large, this can overload the web server such that the response times become slow. |
|||||||||||||||||||||||||||||||
To overcome this, DataPA Enterprise allows the implementation of Processing Agents. The implementation of Processing Agents includes a broker service (the DataPA Enterprise Processing Broker Service) that manages agent processes and agent processes that perform the tasks described above on behalf of the web server.
It is important to understand that there is a performance cost in terms of managing these extra processes and the communication between them. As such, Processing Agents should only be used when the size of dashboards and number of users is causing the response time for the web server to be slow.
If Processing Agents are turned on, they work as follows. When a user requests a dashboard using the web application or mobile app, the broker starts an agent that loads the dashboard on behalf of that user. That agent will remain running with the dashboard loaded until the user navigates away from the dashboard or the idle timeout is reached.
If a dashboard is very large, and so takes a significant amount of time to be loaded, it is possible to instruct the server to pre-load a number of agents with that dashboard. These agents will remain active with the dashboard loaded whilst the server is running. |
|||||||||||||||||||||||||||||||
To enable Processing Agents, follow these steps;
The Processing Agents screen also allows you to set the following configuration settings for the Processing Agents;
To configure a dashboard to be pre-loaded into one or more agents, follow these steps;
|
|