This page sets governance limits on items that can become excessive. Without limitations, these settings can heavily impact the client and system performance NEGATIVELY.
Element Trees Limits
The element trees exposed in the Discover Pro and Discover Lite tools can retrieve enormous hierarchies that can number into the millions of member elements. While this is highly convenient, the size of the data footprint and the handling the browser can overwhelm many client machines and strain the network. As such, it is good practice to limit these.
The limits can be set independently for desktop machines and tablets (which typically have less computing power).
Like element trees, slicer lists exposed in the application can retrieve enormous hierarchies that can number into the millions of member elements. While this is highly convenient, the size of the data footprint and the handling the browser can overwhelm many client machines and strain the network.
- The limit set in the admin is the MASTER limit on slicers for the entire system.
- Slicer limits can then be separately set within User Defaults, which are then assigned to different tenants - but they cannot exceed the master limit set here.
- Next, each user can set their own default slicer limit in their personalized user defaults page (which can not exceed the tenant default).
- Finally, the each slicer used in the system can have a custom limit set through its advanced settings.
The "result limit" is the master setting governing the maximum number of rows that will be returned in any single query from the server to the client. This value can be overwritten by the "Row Limit" option in Discover, per report. But it cannot be exceeded.
Exporting / Printing Limits
These settings control the amount of time to allow the printing and publishing engines to run before timing out.
- Real time - use this settings for user initiated printing / exporting jobs
- Batch time - use this settings for publishing jobs launched via schedules