Report Server Cache Execution Time
The following information provides an overview of InetSoft's reporting software, which is flexible enough to allow users to make the needed changes to improve report server execution time. View the example below to learn more about the Style Intelligence solution.
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.
The 'Data Cache Size' option specifies the number of datasets that can be cached and reused.
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.
|#1 Ranking: Read how InetSoft was rated #1 for user adoption in G2's user survey-based index
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.
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 there are more pages to come.
The 'Minimum Pages' option controls the initiation of page streaming. For small reports that have fewer pages than the minimum, the streaming will be disabled so that end users do not see a partially generated report.
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.)
Several properties are available to control the size of queries returned during preview and runtime operation. These properties provide important safeguards that prevent end-users from erroneously requesting very large amounts of data while designing Worksheets or Ad Hoc reports.
The first group of properties below can be configured from the 'Performance' page in Enterprise Manager.
Other safeguard properties are as follow: