Page History
...
- using AQ_Statistic_Process containers with very broad search criteria (which are matched by many cases)
- using AQ_Statistic_Process containers on pages that are rendered very often by many concurrent user sessions (not recommended on pages accessible for end-users, landing pages, dashboards - anywhere where users will often go but without the specific intent to look at these graphs).
The performance of this container will be fixed in a next minor release.
If you encounter any problems that might be related to this issue please do not hesitate to contact Blueriq support.
Technical Details
When the search criteria of an AQ_Statistic_Process container are matched by many cases, the following actions are executed by the Runtime:
- one database query is made to find the matching cases
- for each batch of 1000 cases, another query is made to retrieve the attributes specified in the criteria
For example, if 100,000 cases match, then 101 database queries will be executed. The impact on performance depends on the hardware configuration, network configuration and load on the database server, and needs to be estimated on a case-by-case basis.
Since the attributes are sent over the network and temporarily stored in the Runtime memory, the memory spike depends on what kind of data is stored in the attributes and how many attributes there are. This also can only be estimated on a case-by-case basis.
UI Expand | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||
|
...