Repository Objects Caching

On Foresight Analytics Platform BI server work, extraction and storage of data required for web application work is made in BI server memory.

The system can be expanded by connecting additional (more powerful) servers with used for data extraction and caching from repository. BI server will request these BI servers and get the thread with required data without additional request to DBMS. To connect additional BI servers, fill in the Service section in the settings.xml file or in system registry settings.

Compiled versions of objects are cached for repository objects. Cache speeds up startup of forms and execution of application code during application projects work.

When compiling units/forms/assemblies, a file cache, which stores a compiled object version, is created on the local disk. When working in Linux OS, cache is located on the BI server in the subfolder opt/foresight/fp10.x-biserver/var/cache/AsmCache<number>/Mod/<repository ID>/<build number>. When working in Windows OS, cache is located by default in the user profile in the subfolder %USERPROFILE%\AppData\Local\Foresight\Foresight Analytics Platform\AsmCache<number>\Mod\<repository ID>\<build number>. If required, file cache storage path can be changed. To do this, in the registry key [HKEY_CURRENT_USER\Software\Foresight\Foresight Analytics Platform\10.0\10.11] create the CachefilePath string parameter and set the required path in it.

Recommendations:

Remember that a modified unit or form is saved when compiled from the development environment. After this it cannot be guaranteed that the previous platform version can open the saved unit or form.
Developed units and forms should be arranged and stored inside the assemblies. This reduces the number of created cache files, which reduces the number of file system calls and speeds up startup of cached objects.
Fore code changes made during user work will be applied only after unloading and repeated loading of complied assemblies. In case of event handler, one will need to close all objects, which use this handler, to apply new code.
Assemblies/units, which code uses static class fields, are unloaded only after exiting the repository, that is why one should log in to the repository again to apply code changes.
Clear assemblies cache in the repository only when there are no active users. This will prevent from unpredictable consequences.
When installing updates with selected Set Date Modified from the Update checkbox, one should force clear assembly cache on all BI servers. It is not recommended to use this setting during the update of development environment objects. It is related with the fact that compilation date and time are stored in assembly cache. To enable recompilation, date and time in cache should be earlier than date and time of object modification in the database. As the database stores time from the update, this condition may be impossible to fulfill.

Cache Clearing

Cache clearing helps avoiding the use of potentially outdated data. Depending on the operating system in use, there are different cache clearing options.

Linux Windows

To clear development environment object cache, run the script to delete files in the subfolder opt/foresight/fp10.x-biserver/var/cache/AsmCache<number>/Mod/<repository ID> of the required repository. Cache is cleared by the BI server administrator.

To clear development environment object cache:

Copy the CacheClearing.zip archive with the check_fcntl, isblock.sh files. The check_fcntl utility checks if cache is locked. The isblock.sh script deletes unlocked caches.
Grant execution permissions for these files:

chmod +x check_fcntl isblock.sh

Set a schedule for running the isblock.sh script in the scheduler, for example cron.

As a result, unlocked caches will be cleared automatically based on a schedule.

Start the isblock.sh script for a single-time clearing.

To clear development environment object cache, select the Repository > Clear Assembly Cache item in the security manager's main menu.

To work with cache of various repository objects in the Fore language, use properties and methods of the IMetabase, IMetabaseObject interfaces. To clear object cache, use the IMetabaseCache.FlushAll method.