Repository Objects Caching

On caching dictionary elements and time series database dictionaries the system creates temporary copies of the object containing element attribute values and links to the used objects on the user computer.

NOTE. Dictionary and time series database element cache is stored and used within the same repository connection.

Caching of dictionaries and time series database is intelligent and available for a number of users if they have similar access permissions and use the same parameter values. It means that several copies of one object can be cached at a time (for example, for various parameter values).

NOTE. It is available to enable In-Memory data caching for dictionaries. Caching mechanism can be changed in the Settings.xml or registry file. Settings are determined on client workstations if the desktop application is used, or at BI server.

Cache provides speeding up start of custom forms and execute application code on application projects work.

On compiling units/forms/assemblies (Fore or Fore.NET), a file cache, which stores a compiled object version, is created on the local drive. By default, cache is located in the user profile, in the subdirectory "\AppData\Local\Foresight\Foresight Analytics Platform\AsmCache<n>\Mod\<Repository ID>\<assembly number>\". If required, file cache storage path can be changed. To do it in the [HKEY_CURRENT_USER\Software\Foresight\Foresight Analytics Platform\9.0\9.2] registry branch create the CachefilePath string parameter and set up required path in it.

To speed up the first starting of application projects on an industrial scale, compiled objects of development environment can also be stored in the repository base. The Caching Assemblies on the Local Disk checkbox is used to control storing mode of compiled objects in the repository base. This checkbox is located in the Repository Parameters dialog box. On the first start compiled versions of objects are copied into the file cache. After that, the rest of the work is performed with file cache.

Possible Consequences

By default, the Cache Assemblies on Local Drive Only checkbox is deselected, the compiled version of object is saved both on the local drive and in the repository.

If different platform versions are used to work within the same repository, and the compiled assemblies are saved to the repository, one project can store forms and units compiled by different platform versions. This may cause errors like Access Violation or Internal Runtime Error, that occur, for example, when a form is started from another form compiled by other release of the Platform. These errors are caused by incompatibility of formats in different platform versions.

This may also slow down development process. On compiling objects on the same computer, their compiled versions are saved into the repository base. If these objects are used at the same time to work on another computer, local compiled versions and repository versions are compared. This will cause constant detecting of differences, which in turn will overload server because versions are constantly loaded the local disk and unloaded back to the repository base.

Solution

To avoid such consequences:

• Select the Caching Assemblies on the Local Disk checkbox at the stage of project development

• Delete complied assemblies from repository.

Recommendations

• On developing application code, select the Caching Assemblies on the Local Disk checkbox. This will enable the user to work with code in different platform versions.

• It is not recommended to select the Caching Assemblies on the Local Disk checkbox if the system is installed on the users' workstations belonged to a customer.

• Remove compiled assemblies from the repository before commissioning the system to a customer. Then deselect the Caching Assemblies on the Local Disk checkbox and start users' forms to compile and save assemblies in the repository. The users' forms must be started with the platform version, which will be also installed at customer's place in the future. This will prevent compiling objects on decompressing and first starting of the system, as the previously compiled objects are loaded into the file cache.

• In order not to prevent users from working in the system, when the system is developed for a customer, it is necessary to select the Caching Assemblies on the Local Disk checkbox on the workstations used for development.

• Remember that a modified unit or form is saved when compiled from the development environment. After this it cannot be guaranteed that a previous platform version can open the saved unit or form.

• Developed units and forms are recommended to be arranged and stored inside the assemblies. This reduces the number of created cache files that reduces the number of file system calls and speeds up start of cached objects.

• Selection or deselection of the Caching Assemblies on the Local Disk checkbox does not slow down general development process, as in any case file cache is used at the start. This checkbox can have influence only at the first start and decompressing of a new version of application on the customer's computers.

On caching of regular report instances of an object are created, which are opened with certain parameter values. On opening an object with some parameters the cache is checked for availability of a record corresponding to these parameters. If such a record is found, cached object version is extracted and opened. If no record is found for the specified parameters, the last object version is opened from the repository. All the objects, on which this object depends, are also opened. Instance cache of the regular report is stored in repository base. Caching is managed in the Object Cache dialog box.

To speed up map rendering in reports, maps are cached. When the report is opened, it is checked if its cache contains a map. If the map is found in cache, the cached map will be shown in the report. If there is no map in cache, the repository map opens, and cache will be refreshed.

If there are several connections to the same repository, one common cache with maps will be used for all connections. On closing all connections, cache of maps is cleared.

On selecting object view in the object navigator as large icons images are cached for preview. Icon caching is used only for reports created by means of the Dashboards, Analytical Queries (OLAP), Reports, Time Series Analysis tools.