{"id":24203,"date":"2024-02-15T14:53:34","date_gmt":"2024-02-15T22:53:34","guid":{"rendered":"https:\/\/docs.extraview.com\/v25\/book\/pre-caching-layouts-upon-system-restart-1\/"},"modified":"2025-02-14T10:43:56","modified_gmt":"2025-02-14T18:43:56","slug":"pre-caching-layouts-upon-system-restart-1","status":"publish","type":"page","link":"https:\/\/docs.extraview.com\/v25\/extraview-25\/administration-guide-1\/advanced-menu-1\/pre-caching-layouts-upon-system-restart-1\/","title":{"rendered":"Pre-Caching Layouts Upon System Restart"},"content":{"rendered":"

When a layout is first accessed, either upon a restart of the application server, or upon a change to the layout by the administrator, it is read by ExtraView, and compiled into a form that can be rendered speedily. This action may take a half-second for simple layouts to many seconds for complex layouts.<\/p>\n

This feature is controlled by the security permission key named SE_TEMPLATE_PRECACHE.<\/p>\n

If you do not want an end-user to face this delay when they are the first person to access a layout, you can use the utility at Fields & Layouts<\/b> –> Controls pre-caching templates at system startup<\/b> to compile and cache layouts when the application server is restarted.<\/p>\n

<\/p>\n

Pre-caching Layouts<\/span><\/p>\n

ExtraView has an overall limit of 100 layouts held in the cache at one time, and if this number is exceeded, then the oldest layout is removed from the cache. At the same time, there is a cost in time to pre-cache layouts, therefore the recommendation is to only pre-cache layouts if a user is likely to complain about the time taken to reach the layout if they are first person to use it.<\/p>\n

To pre-cache layouts, use the filters at the top of the screen to select the layout(s) you want to cache. This will be a combination of user role, business area, project, layout type and the locale with which the layout is to be displayed. Once you select the filters, use the Add Selected Keys<\/b> button to add the layouts to the pre-cache list. You can remove layouts individually using the Del<\/b> button, or you can set up keys and remove a list of layouts at one time.<\/p>\n

The caching is controlled by a system task named TEMPLATE_LOADER. This task must be started in order for the caching to take place. Go to the Manage Tasks and Threads<\/b> administrative utility and Add<\/b> the task. The task should be set up to run on each node of a clustered system. It is recommended that you set the poll interval to zero. This causes the task to run once upon system startup and not to be run again.<\/p>\n

Caching layouts is somewhat tricky, as a full understanding of exactly what needs to be cached to speed up the initial load time is essential. Some recommendations:<\/p>\n