This page sets governance limits on items that can become excessive. Without limitations, these settings can heavily impact the client and system performance NEGATIVELY.
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.
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
- Proactive Garbage Collection: automatically free up memory by removing unused items. Every half-hour, Pyramid will check if there are unused items; if so the garbage collection will run. The garbage collector can also be run for a specified service from the Summaries Panel, or for all services from Server Instances.
- Proactive Renderer Collection: automatically clear printing processes every half-hour to free up printing services.
These setting govern the size of files that can be uploaded to the application. They usually affect Model, since users upload large data files for processing. Buffering governs the size of the 'chunks' that the uploader will accept each time a piece of the source file is uploaded.
Note that setting the file size too high can overload the web servers and client browser. If large files need to be imported it is usually better to use a network reference to those files instead.