Real-time report with good cache real and real time reporting

How can you actually get faster access to your reports without increasing the burden on your servers?

If you repeatedly access the same report repeatedly, the server's operation consumption will increase, and the time required for the presentation of the report will grow. If you can cache the first calculated report and read it directly from the cache when it is accessed again, this can reduce the burden on the server, thus reducing the user's waiting time. The Fast-Yi report provides a mechanism for caching, which enables real-time reporting by setting the cache parameters in Reportconfig.xml to control the use of the cache.

　　

The cache parameters are provided in Reportconfig.xml, and I'll give you a detailed explanation:

　　

Alwaysreloaddefine: Whether to re-read the report definition each time, such as set to Yes, to turn off the cache function, set to No, indicates the caching function.

　　

Cachedparamstimeout: Represents the time, in minutes, that the parameters submitted to the report are saved in the cache. If this parameter is not set, the default value is 120 points.

　　

Cachedreportdir: The folder that represents the report cache (on UNIX systems, users should have write permission to this folder and allocate a reasonable amount of space based on the number of reports and the size of the traffic and the time the cache times out). If this parameter is not set or the setting is incorrect, the JDK default temporary folder is used.

　　

Cachedidprefix: Represents the prefix for the report cache. Settings are required only in a clustered environment and when multiple servers share a single report cache directory.

　　

Cachedreporttimeout: Indicates the time, in minutes, that the report cache is saved. If this parameter is not set, the default value is 120 points. This value should be adjusted based on actual memory size, cache folder space size, typically between 1-3 hours.

　　

When and only if the Alwayreloaddefine property in Reportconfig.xml is set to No, the report caching feature is turned on, and when it is calculated, the report definition file is loaded only once for the specified time, and the report is evaluated only once. Other operations are extracted from the cache, such as page flipping and so on.

　　

The cache set in Reportconfig.xml will work for all applications. When the Alwayreloaddefine property in Reportconfig.xml is set to No, all reports in the app will have the cache feature. We can also set the individual report to have the cache function through the label.

　　

The properties in the tag tag are described below:

　　

UseCache: Controls whether caching is enabled. The UseCache setting only works if and only if the Alwayreloaddefine property in Reportconfig.xml is set to No. When UseCache is no, even if the Alwayreloaddefine property is no, the report published by this label does not turn on the caching feature.

　　

Timeout: The number of minutes from the cache system to generate a report, if not within this time, a new report is generated. The timeout setting only works if and only if the Alwayreloaddefine property in Reportconfig.xml is set to No. If the timeout is set in the Cachedreporttimeout and the timeout in the label is inconsistent, the timeout setting is the primary.

　　

Examples of label use are as follows:

　　

Reportfilename= "Test.raq"

Usecache= "Yes"

Timeout= "30″

/>

　　

The Fast-Yi report provides the ability to flexibly control the cache usage by configuring the cache parameters in the Reportconfig.xml, greatly reducing the pressure on the server to access the report frequently when the data volume is large, realizing the real-time report and enhancing the user's experience.

Real-time report with good cache real and real time reporting