4.9.1 Performance Options and Safeguards
The options on the 'Performance' page should be set according to the server's memory size and the performance characteristics of the application.
• Maximum Concurrency: The 'Maximum Concurrency' property specifies the maximum number of sessions allowed at any given time. Concurrency is the number of simultaneous user sessions that the report engine will support. A user session is initiated when the user logs in, and terminates when the user logs out or when all the reports associated with the user's session time out.
• Ad Hoc Timeout: The 'Ad Hoc Timeout' setting specifies the maximum amount of time allowed for Ad Hoc report requests. The timeout setting may not be honored by all databases. The corresponding sree.properties entry is query.adhoc.timeout. See Ad Hoc Reporting for more information.
• Ad Hoc Maximum Row Count: The 'Ad Hoc Maximum Row Count' setting specifies the maximum number of rows retrieved for Ad Hoc report requests (preview or final report). The maximum row count setting may not be honored by all databases. The corresponding sree.properties entry is query.adhoc.maxrow. See Ad Hoc Reporting for more information.
• Query Timeout: The 'Query Timeout' setting specifies the global timeout (seconds) for all queries during report/Viewsheet runtime execution. The timeout setting may not be honored by all databases. The corresponding sree.properties entry is query.runtime.timeout.
• Query Maximum Row Count: The 'Query Maximum Row Count' setting specifies the global maximum size for all queries during report/Viewsheet runtime execution. The maximum row count setting may not be honored by all databases. The corresponding sree.properties entry is query.runtime.maxrow.
• Table Maximum Row Count: The 'Table Maximum Row Count' setting specifies the global maximum size for all tables during report/Viewsheet runtime execution. The corresponding sree.properties entry is table.output.maxrow. This property controls the maximum size of the final displayed table, following any grouping and aggregation.
• Report Maximum Page Count: The 'Report Maximum Page Count' setting specifies a global maximum on the number of pages for reports during runtime execution. The corresponding sree.properties entry is report.output.maxpages. You can override this global setting for a particular report by setting a 'Max Number of Pages' value in the 'Report Properties' dialog box of Style Studio. See Report Properties in Report Design for more information.
• Composer Live Data Timeout: The 'Composer Live Data Timeout' setting specifies the maximum amount of time allowed for 'Live Data' requests in Visual Composer. The timeout setting may not be honored by all databases. The corresponding sree.properties entry is query.preview.timeout. See Showing Live Data in a Table in Data Mashup for more information.
• Composer Live Data Maximum Row Count: The 'Composer Live Data Maximum Row Count' setting specifies the maximum number of rows retrieved for 'Live Data' requests in Visual Composer. The maximum row count setting may not be honored by all databases. The corresponding sree.properties entry is query.preview.maxrow. See Showing Live Data in a Table in Data Mashup for more information.
• Create MV on demand: Specifies that a new materialized view should be automatically created (on-the-fly) for any Viewsheet that does not already have a materialized view defined. The materialized view will supply data to the Viewsheet both at design time and at runtime. See Materialized Views for further details.
• Use meta-data for editing if MV is not available: Specifies that when a materialized view is not available to supply data for a Viewsheet (for any reason), the design mode of Visual Composer should display meta-data rather than querying the database for data. This will improve design-time performance. See Suppressing Query Execution in Design View in Dashboard Design for more information about meta-data mode.
• Fail if MV is not available at runtime: When a user loads a Viewsheet in the User Portal, this option generates an error message if the requested Viewsheet does not possess a corresponding materialized view. If you want the Viewsheet to query the database for the needed data in this case (rather than generate an error), disable this option.
• Cache Interval: The 'Cache Interval' specifies the elapsed time (ms) between cache swaps. At the specified interval, the server checks, swaps, and prunes cached pages according to their age and access time.
• Workset Size: A “workset” is a group of report pages that can be swapped as a single unit between RAM and disk. A large workset size provides for more efficient disk swapping. However, a large workset size may also delay initial report availability because the report engine assembles the full workset before it begins streaming pages for display.
• Maximum Reports Per Session: The 'Maximum Reports Per Session' option specifies how many reports a session can open and keep active. If a session contains more active reports than the threshold, the older reports are destroyed to conserve memory.
• Cache Security Provider Data: The 'Cache Security Provider Data' option, when set to 'true', enables the caching of user, role, and permission information. This is recommended.
• Security Cache Interval: The 'Security Cache Interval' option specifies the interval (in milliseconds) after which the cache of user, role, and permission information is automatically cleared.
• Dataset Caching: The 'Dataset Caching' option specifies whether query results are cached and shared across reports and/or Viewsheets. If the option is disabled, then the query results are only shared within the same report and/or Viewsheet if multiple elements are bound to the same query.
• Data Cache Size: The 'Data Cache Size' option specifies the number of datasets that can be cached and reused.
• Data Cache Timeout: The 'Data cache timeout' controls the persistence (ms) of a dataset in the data cache. If the dataset is not used for the specified time period, it is removed from the cache. The default timeout is 30 seconds.
• Paging Threshold: The 'Paging Threshold' setting controls the initiation of dataset paging. If a dataset exceeds the threshold, it is paged to disk in order to conserve memory.
• Page/Data Streaming: The 'Page/Data Streaming' option allows reports to be processed in parallel with data loading. If the 'Page/Data Streaming' option is checked, the engine begins processing the report when data becomes partially available, resulting in quicker report display. Users may see a partially completed report marked with a “*” in the page total, indicating that additional pages are still being generated.
• Minimum Pages: The 'Minimum Pages' option specifies the number of pages to generate before initiating page streaming. If this value is less than the workset size (see above), streaming will begin only after the first workset has been fully generated. However, you can enter a value of “1” to force the first page of the report to display immediately, regardless of workset size. For small reports that have fewer pages than the minimum, streaming will be disabled so that end users do not see a partially generated report.
• Clear Security Cache: The 'Clear Security Cache' button clears the cache of user, role, and permission information. This is useful if security information has changed and you wish to manually refresh the server cache. (Note: The cache is automatically refreshed at the interval specified by the 'Security Cache Interval'.)
• Clear Cube Cache: The 'Clear Cube Cache' button deletes the cached OLAP cube structure. This is useful in the event that the cache becomes corrupted, which might occur if the application server fails to terminate properly. (An error such as “Locking failed due to time out” is a possible symptom of this.)
See Also
Appendix B.4, Web Properties and Safeguards, for property descriptions.
| << 4.9 Tailoring Server Performance | © 1996-2013 InetSoft Technology Corporation (v11.4) | 4.9.2 Limiting Query Size and Execution Time >> |